Introducing the New IRE Resource Center

By • • Investigative Reporters and Editors in Zoom

Slides

Show the extracted slide text

Slide 1

archive.ire.org
The next generation of investigative knowledge sharing

Slide 2

33,449 resources
Now available in a new searchable database

Slide 3

What you'll find
Thousands of contest entries, tipsheets and training materials

Slide 4

What we've got
Some fields are better than others

Slide 5

Semantic search
AI helps find matches based on the meaning of your words

Slide 6

Tune the results
Controls allow you to filter and sort

Slide 7

Discover new things
AI recommends related documents

Slide 8

Members only
Restricted to active members with an ire.org account

Slide 9

The software stack

Vercel frontend
SvelteKit: Static single-page application consumes JSON data

Fly.io backend
FastAPI: Python application supplies JSON data
Redis: Caching layer enforces ire.org membership wall
Qdrant: Vector database indexes with semantic embeddings

Slide 10

Work in progress
Report problems to help@ire.org

Slide 11

What's next

1. Create staff tools: Empower IRE staffers to update the database
2. Complete the migration: Upload the 10% of resources that aren't indexed yet
3. Tidy up: Reconcile imperfections in the metadata
4. Add audio transcripts: Integrate text from thousands of recordings transcribed by AI

Slide 12

Your humble servants
Tell us what stinks so we can make it better

Ben Welsh: b@palewi.re
Derek Willis: dwillis@gmail.com
Cody Winchester: cody@ire.org

Recording

Show the timestamped transcript
  1. And we'll get this webinar rolling.
  2. Welcome everybody here.
  3. My name is Cody Winchester.
  4. I am the director of technology at IRE.
  5. Thank you for coming to hear about our brand new resource center.
  6. I'm going to be handing this over to Ben Welch here in a minute.
  7. He and, or the colleague, Derek Willis have been working on,
  8. if you have not seen it, I'm going to drop a link in chat, archive.ire.org,
  9. which is our new repository for contest entries, tip sheets,
  10. all sorts of resources.
  11. We are working on supplementing that as we go.
  12. And Ben, you just recently described this as our 1.0 version.
  13. We're looking for feedback.
  14. So please kick the tires and let us know what you think.
  15. And I know this recording will be made available afterward
  16. for anybody who has to leave early or wasn't able to make it.
  17. And otherwise, I'm going to turn it over to Derek,
  18. chair of the board's website improvement task force,
  19. who's done quite a bit of work to make these resources more accessible.
  20. Thanks.
  21. Thanks, Cody.
  22. And thanks, everybody, for being here.
  23. Really, what I want to, the way I want to begin is by talking about,
  24. like, we, I think, all know or like have an idea of like how valuable
  25. the resources that come out of our IRE's trainings and conferences
  26. and contests are.
  27. And like, if you've been a member or been around the organization
  28. or been to one of the conferences, you know that like you go,
  29. sometimes a lot of these sessions you go to for the tip sheets.
  30. The tip sheets are great or the contest entries are great.
  31. You're like, wow, I really want to know how they did that.
  32. And so the effort that our task force and in particular Ben worked on,
  33. has been working on for the last year,
  34. is about trying to harvest that knowledge and that context
  35. and make it accessible to the IRE membership.
  36. And so to that end, like, thanks to the efforts of Cody and other folks
  37. in terms of getting us, you know,
  38. digital representations of conference tip sheets, of contest entries,
  39. we're able to now have a archive site for those and that allows user
  40. and IRE members to search for interesting things, for useful things,
  41. for like, oh, hey, I remember this session from this conference
  42. and I want to find that tip sheet or I want to see, you know,
  43. what's been done on this topic and all the, you know,
  44. all the contest entries that we have and, you know, other kinds of materials
  45. from our conferences, IRE's conferences and trainings.
  46. And so that's kind of what we've built with the archive site.
  47. And so we want to kind of show that off and talk a little bit about
  48. what that entails.
  49. Ben, can you do me a favor and just drop in like the presentation link,
  50. because I think I've misplaced it somehow.
  51. I sure can.
  52. And I am clear of the thing I had to watch out for.
  53. Oh, well, then if you'd like to, you give a much better spiel on this
  54. than I do, but it's up to you. I'm happy to.
  55. Let's, I'll pull it up and then let's do edit like Kenny and Dolly.
  56. That sounds great.
  57. All right. Can you guys see my screen?
  58. Yes. Excellent.
  59. So, yeah, you heard it from Derek. There's a brand new website.
  60. We launched it at the night car conference in Indianapolis.
  61. You can go to it now if you'd like at archive.iree.org.
  62. It's our new resource center.
  63. And I'm going to tell you how it works.
  64. You can see here on the homepage, which is what you'll see after you log in.
  65. When you first go, you should be prompted to sign in because this is members only.
  66. After you log in, you get a big search box.
  67. And if you type in your own name or the subject of whatever you're working on
  68. at your job right now or whatever you're interested in,
  69. you should get back a list of related IRE resources.
  70. Each one, there's about 33,000 that are currently in the database.
  71. And each one of them has its own sort of detail page or URL
  72. where we present everything we have for that resource, which, you know,
  73. has its name, who came up with it, what type of thing it is.
  74. And then in most cases, we have the associated thing itself,
  75. be it a PDF of the tip sheet that was scanned in or emailed over
  76. or an audio recording of a panel or other event.
  77. Those are the two most common things.
  78. And so 33,000 are in there.
  79. What you'll find if you go in there, if you fish through it,
  80. is that the majority of them are IRE contest entries.
  81. So, you know, through the years when people have applied to win an IRE award,
  82. they've had to fill out a form that explains, you know,
  83. why they should win and talks about the method behind their work.
  84. And that actually accounts for the majority of the 33,000
  85. are those contest entries, which stretch back decades.
  86. In preparing this site, I heard from some of our members
  87. who are passionate users of the contest entries.
  88. I can share with you a couple use cases I heard about
  89. from real world investigative people.
  90. One is an editor here at Reuters who told me that he uses the database
  91. to look for and sniff around topics that he's interested in exploring
  92. and maybe investigating.
  93. And what he'll do is look for maybe classic examples
  94. that he hadn't heard of from decades past.
  95. Maybe they're localized in different places
  96. and ask himself, could I nationalize the story
  97. or is there some lesson I can learn from what's been done in the past?
  98. It also allows him to see whether other people have already covered the waterfront
  99. or whether there might be new stuff to look up.
  100. His view is that newspaper archives are so decayed
  101. and the internet is so biased towards the present
  102. that he often can't find the same information when he searches in Google
  103. and that looking at the contest entries gives him a more direct look
  104. at what investigative reporters and editors have been doing.
  105. So that's one case.
  106. Another case I heard was from people applying for awards.
  107. So you could look at the applications from the previous year
  108. and say, hey, who won and why did they apply
  109. and what things did they emphasize or not?
  110. And that can help you write a better package yourself.
  111. That was another tip I heard.
  112. And then a third use case, which I did not anticipate
  113. but makes a lot of sense,
  114. is I think a number of journalism educators use the contest entries
  115. to help their students learn about the methods and practices
  116. of kind of like the great stories in IRE history.
  117. So if you're having your students study the Boston Globe
  118. child sexual abuse story
  119. or pick your greatest hit of investigative journalism,
  120. if you find the contest entries for those stories,
  121. you can often get a lot of insider detail about how the data analysis
  122. was done or the story was put together, the kind of behind-the-scenes stuff
  123. that could be really helpful for students to learn.
  124. So that was the third interesting use case I heard about contest entries.
  125. The number two most common thing in the database are, of course, the tip sheets,
  126. which I suspect are the most popular.
  127. I don't have data to back that up, but that's going to be all the materials
  128. presentations through the years with the PDFs attached.
  129. We have 6,000 of those assembled there in this data set.
  130. There are a few duplicates and kind of reruns from year to year,
  131. but it's pretty fresh, pretty fresh and pretty unique.
  132. And then the third large group are the audio recordings.
  133. These are all the panel discussions and events that happen at IRE conferences.
  134. A large share of those are put down to tape,
  135. and you can listen to MP3s of Bob Woodward and Leonard Downey
  136. talking about this or that,
  137. or Sarah Cohen schooling you up on the database frame of mind way back when.
  138. You also are able to listen to the audio recordings of more recent events as well
  139. and find stuff related to topics you're interested in.
  140. And for me, as someone who was really exploring this archive in depth
  141. for the first time making the site,
  142. I had a lot of fun going back and listening to some of the older stuff
  143. and tuning into the golden oldies.
  144. Every asset in here has a common set of metadata
  145. or columns in the spreadsheet that go with each record,
  146. and some are filled in better than others.
  147. This is not a perfect data set.
  148. This release we're doing is really a first effort
  149. just to get this stuff up and out,
  150. and there's a lot of room for improvement.
  151. And this is one of those areas where we think we can improve.
  152. You can see why everything has a category and a title and description.
  153. Our author's field isn't very well structured or formatted.
  154. It's a little loosey goosey.
  155. And we've got some pretty big gaps as far as the year or date
  156. when the records were created,
  157. which means that when you do a search and try to sort
  158. for what the most recent document is,
  159. which is a really common use case we heard from people,
  160. we don't have a perfect solution yet.
  161. And that's something we want to get better at
  162. bringing up these numbers that you see here on this chart
  163. is one of our goals,
  164. and we want to gradually add more and more extra stuff on as well.
  165. I will jump in here to say that this is much more
  166. of a problem of a past resource problem.
  167. The efforts of the staff have really helped us have more data,
  168. more metadata information about more recent resources,
  169. tip sheets, conference entries, things like that.
  170. But there are quite a few resources from older conferences,
  171. events where that information isn't present.
  172. And oftentimes that affiliation, which is one of the lowest ones,
  173. essentially that's being extracted from people's names
  174. and information on, say, a tip sheet.
  175. And in those cases, if there wasn't really a standard,
  176. people might just put their names and emails on a tip sheet.
  177. And so there's literal cases where the information isn't there
  178. and we have to either sort of derive it
  179. or maybe we won't get it,
  180. or we have to wait until someone might claim it.
  181. Yep.
  182. And this database that you can search with uses
  183. what's called semantic search.
  184. And so this is kind of an AI-flavored version of search
  185. that goes a little beyond just doing kind of strict keyword matching
  186. of what you're putting in.
  187. Kind of under the hood, inside the database,
  188. we've had a machine learning system kind of break up each asset
  189. into kind of its component parts
  190. using the kind of fancy vectorization and AI stuff
  191. we hear so much about these days.
  192. And that allows it to take your query, what you search in there,
  193. and find something closer to what you really mean.
  194. And it also allows us to sort of rate documents
  195. based on their similarity to each other
  196. and other interesting things.
  197. All of the code that does this is open source on GitHub
  198. on the IRE apps profile page, if anyone's interested.
  199. And you can see the Python code we do.
  200. I'd be happy to get nerdy in the question and answer portion
  201. and go into the details of this,
  202. but I don't want to bore you too much.
  203. But we can brag and say we do have an AI-enabled search,
  204. which is pretty cool and was a big learning experience
  205. for me putting this together.
  206. After you do your search, you see a result page kind of like this,
  207. which takes the result of that AI funnel
  208. and says, here's what we think are the best matches for you,
  209. which you then can pick and see from the list how you like.
  210. You're able to tune that search by, say,
  211. limiting it to different categories.
  212. Say you only want to search tip sheets or audio.
  213. You're able to just check and uncheck those boxes and do that.
  214. You're allowed to sort newest and oldest in addition to relevance,
  215. but it is imperfect due to those gaps in the data currently.
  216. And if you really, really hate AI,
  217. you can just turn it off there with that little switch
  218. and do a standard keyword search as well.
  219. At the bottom of each of pages, each assets page,
  220. you can see some recommended similar documents.
  221. This is based on that same AI sugar where we're able to say,
  222. you know, this one is most similar to that one and on and on.
  223. I did have an AI bot make these similar scores for my slide,
  224. and I can see that it has titled one,
  225. a guide to ass kicking in the 90s.
  226. I just noticed that.
  227. I don't think that's a real tip sheet.
  228. Maybe it is a real tip sheet. I don't know.
  229. We'll have to look that one up.
  230. As we said at the start, this is member walled.
  231. So just registering with the IRE website is not enough to access this database.
  232. You have to both be registered and have an active membership,
  233. aka have paid your dues in the last year.
  234. If you don't do that, you can't get it. Sorry.
  235. And this is the kind of software tools we're using.
  236. We're using kind of a vectorized database,
  237. which is a newfangled thing to kind of build.
  238. And this site, I began, I'd be happy to talk about the tech later
  239. if people want to get into it.
  240. But, you know, just to wrap up,
  241. I just want to say this is a work in progress.
  242. It's a very simple search that has a couple interesting features,
  243. but there's so much more we probably can and should be doing with this.
  244. We want to hear your feedback on what's broken or not like it should be.
  245. We want to hear your feature requests on what it should be doing, that it's not.
  246. And if you're really passionate about this,
  247. we would love to welcome you into our volunteer creation process.
  248. We have a sort of list of priorities going forward.
  249. Our top priority is to expand this system to make it possible for the IRE
  250. staff to do rolling incremental updates.
  251. Currently, we're just able to do like big database dumps every so often in
  252. that requires like me or Derek to push a button or Cody.
  253. And we'd rather have like an administrative panel
  254. where the staff can be actively improving it.
  255. That's our top priority.
  256. We're going to do that in the coming months.
  257. But then we also have some gaps in the data,
  258. stuff that was lost in the migration, some of these flawed fields.
  259. We want to try to start cleaning that up.
  260. And then finally,
  261. we have some really interesting stuff associated with the assets.
  262. We haven't integrated yet like the OCRing of all the documents,
  263. the transcribing of all the audio files.
  264. We do have all those associated transcripts,
  265. but we have not yet integrated those into the search or the interface.
  266. You can't see them on the site.
  267. Your search doesn't benefit from them.
  268. And we'd really like to get around to that before too long too.
  269. So that's kind of our roadmap.
  270. The whole thing was done on a volunteer basis by really the three of us
  271. and our colleagues on the volunteer task force.
  272. So be nice to us because this was a nice weekend thing.
  273. But we definitely also want your brutal honesty about how it can
  274. and should be better as well.
  275. And that's really my spiel.
  276. And I don't know if Cody has an agenda beyond this,
  277. but I'd love to hear from folks of what they think about it,
  278. how they use the IRE archives and how we can make them better.
  279. No, let's go ahead and open it up if people want to chat.
  280. Okay, I can get us started.
  281. Hi, everybody.
  282. Thanks so much for sharing.
  283. Well, for building the tool or for sharing it with everyone.
  284. One piece of feedback I gave in the Slack that I wanted to follow up on
  285. was categorization or the possibility of categorization.
  286. I had mentioned that for me as someone who is new to journalism,
  287. I'm not aware of what I don't know.
  288. And so even coming up with what to search for is hard
  289. when I'm presented with just a search bar on the homepage.
  290. So definitely something like that would be really helpful
  291. as a future request for me.
  292. You'd be interested in kind of browsing topics you're interested in.
  293. Am I hearing that right?
  294. Exactly.
  295. Yeah, we've heard that you're not the only person who said that.
  296. You know, we had several other people at NyCar raise the same question.
  297. They're kind of like, I want to nose around.
  298. I want to walk through the stacks a little bit, you know.
  299. And I could imagine, you know, we don't currently have kind of tags
  300. or categories beyond the sort of like, this is a tip sheet.
  301. This is a contest entry level stuff.
  302. And so getting that, like applying those groupings
  303. is like something maybe AI can help us with or I don't know what.
  304. Like, so that's a challenge.
  305. And we were actually talking about that earlier today.
  306. Like, how could we do that in a disciplined way?
  307. A second idea we've heard, I wonder what you would think of this,
  308. is maybe having the IRA staff or muck rock or members of the community
  309. curate kind of like maybe greatest hits kind of lists,
  310. like a reporter who really knows a topic or someone on the staff
  311. collected the 10 best tip sheets on topic X
  312. and it was a little more of a DJ playlist.
  313. Does that appealing or how do you react to those ideas?
  314. Yeah, I mean, I would definitely love something like that.
  315. I think if those curated lists could still also link to the non,
  316. the top, you know, top 20 or 10 to 20, 20 to 30 of whatever else is left.
  317. So I could then follow up with other things.
  318. I think that would be really helpful.
  319. But as a place to start, for sure, I would love to see something like that.
  320. Yeah.
  321. And I'm assuming it's also tricky because language changes over time too.
  322. So the way something is described in the 90s maybe is described with using
  323. different words now.
  324. So I'm sure it's a challenge.
  325. That's an interesting question.
  326. There's a PhD thesis for you, Derek.
  327. I mean, there's a lot of, I'll pass, but there's a lot of like,
  328. there are definitely sort of topics or specific phrases or techniques
  329. that kind of die out for not extinction level stuff,
  330. but in terms of like what IRE members talk about.
  331. Yeah.
  332. It's like as if that were the case that essentially like we used to talk
  333. about these things and now we don't talk about that specific thing anymore.
  334. We've replaced that with something else or we've, we've moved on.
  335. So there's definitely a, a life cycle to some of these, some of these things.
  336. I, I, you know, not like mostly not for things like if you're browsing by,
  337. like I want to do the story on this kind of institution or things like that,
  338. or I'm interested in what's been done in this area.
  339. Like probably that's fine, but like there's definitely some specific
  340. technique stuff that is either, that is basically now mostly dead in terms
  341. of like we have, like we have a lot of people talking about it, but like,
  342. like there are a lot of tip sheets in there on how to search the internet.
  343. Right.
  344. And right.
  345. And now maybe somebody would use the word OSINT if they're talking about
  346. talking about like, yeah.
  347. And so like, and so like, but I mean, I do think that like Ben,
  348. like the semantic aspect of this search engine does handle some of those
  349. use cases where like, if I'm describing what we now call OSINT probably
  350. should find that stuff anyway.
  351. Right.
  352. Or a car versus data journalism, that kind of thing.
  353. I think it's like, like that's, that's where like, that's the whole,
  354. that's the whole ball game for semantic search.
  355. That's why you use it is to be like, I.
  356. Yeah.
  357. Like it could appear in all these different ways.
  358. So.
  359. Yeah.
  360. Cool.
  361. Thank you.
  362. Um, once I could follow up one small bug that I have noticed so far is if I
  363. click on, I haven't pulled up, if I click on an item and I see that there's
  364. a category tip sheet or audio, if I click on it,
  365. it just takes me back to the homepage search bar rather than I was,
  366. I was like, I was expecting, I guess I would say like a list of all the audio
  367. ones or all the tip sheets kind of in one spot.
  368. That's what it should be doing.
  369. I mean, yeah, like, like, oh no, no, she's absolutely right.
  370. Like I just tried it with contest entry and it just goes right back to the
  371. homepage.
  372. This is like one of my Svelte kit bugs.
  373. Yeah.
  374. Where like, you know, you're trying to do that.
  375. I don't want to drag you into my JavaScript life, but like,
  376. this is something that like where it'll work on your local development.
  377. And then not when you build it out on versatile Derek and like,
  378. there's like little things like that, that I, that it's good people point out.
  379. So, wow.
  380. Should we just like assign AI to do this right now?
  381. Get on it, Claude.
  382. I mean, probably.
  383. I'm doing it right now.
  384. Other, other thoughts.
  385. Yeah.
  386. We went here.
  387. We want your bug reports.
  388. Thank you so much for that.
  389. That's really helpful.
  390. Thank you.
  391. Thank you.
  392. Thank you.
  393. Thank you.
  394. Thank you.
  395. I'm curious to know if folks have thoughts about how we should,
  396. or whether or how we should handle.
  397. Not whether, or essentially how we should handle.
  398. We have like, we've got some amount of non-English language.
  399. Resources, right?
  400. Yeah.
  401. We, we, we do have some number.
  402. They're not currently categorized that way.
  403. And a lot of the.
  404. A lot of the backlog that we have to load into the database from the last
  405. couple of years, we have quite a bit more mostly Spanish language content.
  406. But being able to categorize by language is another.
  407. I mean, when we're, when we're talking about, you know,
  408. What does the process look like when we're loading new resources into the
  409. database, being able to categorize by language is one of,
  410. is one of our, on our wish list.
  411. Okay.
  412. Other thoughts or.
  413. Or future suggestions or.
  414. We'll make this more useful.
  415. Beyond brow, beyond browsing, which we definitely now hear.
  416. Silvia, I just linked you to the issue where AI has been assigned to pick
  417. it up. If you're interested in.
  418. Co-pilot as a spectator sport.
  419. Let me know if I got the description of the bug wrong. I think I got it.
  420. But yeah.
  421. Hi.
  422. Hello. Hello. How are you?
  423. I'm great. Thank you. And thank you for organizing this.
  424. I found really useful.
  425. I don't know if it is already possible or covered,
  426. but I was wondering if.
  427. There might be like a connection in database.
  428. If a story won an award,
  429. one of like a Pulitzer award or,
  430. or another award. And so you can have that.
  431. Like the, the most important,
  432. the category of the awarded stories.
  433. Hmm.
  434. That's a good, like,
  435. that's a good idea for one of these curated lists, right? Or you, you know,
  436. you would say here, here's like,
  437. here's all of last year's winners, right?
  438. Maybe you're something like that or.
  439. And then.
  440. Sorry. And then it might be interesting.
  441. If the authors or someone else will write.
  442. A behind the scene.
  443. A story of the story.
  444. About the tools used.
  445. The method.
  446. The methodology and the tools.
  447. These will be the real value.
  448. I think I don't know if the other.
  449. Agree.
  450. So we do have like, well, I mean,
  451. first of all, we, we kind of used to have for,
  452. for like technical sort of methodological stuff.
  453. We, we.
  454. I already sometimes will.
  455. You know, obviously there's,
  456. there's some panels and sessions about that that go into some detail
  457. about that.
  458. This is also what we used to use uplink for in a lot of cases.
  459. Or in some cases, at least a description of it.
  460. Uplink was like this older newsletter that we had.
  461. And.
  462. And I think we're going to be able to,
  463. at least one of my goals is to be able to integrate the,
  464. the text of uplinks into there.
  465. As well.
  466. But I do think that like.
  467. There's a.
  468. Like.
  469. Like the, the, the, I think the challenge,
  470. one of the challenges for that is that there are like the tip sheets
  471. are usually like a summer and even the conference presentations
  472. themselves are usually a summary of that rather than like a play by
  473. play.
  474. So.
  475. Oh, we're bringing back.
  476. I read your.
  477. Oh, all right.
  478. Nice uplink returns. Great.
  479. Great.
  480. But I do think like one of the issues was sort of like, I guess it
  481. depends.
  482. How detailed do you want that methodological stuff?
  483. To be.
  484. Because a lot of times we don't get all,
  485. we don't really have all of that as part of our resources.
  486. Okay. Thank you.
  487. It might be interesting also to involve the voters of the,
  488. of the stories.
  489. So we would like,
  490. we would like people to be able to like members to be able to claim
  491. resources that they've uploaded.
  492. You know, it's sort of been like, you know,
  493. if you go like to a member's page,
  494. the member directory and be like, Hey,
  495. I've got here are the resources from this member.
  496. And like, I, you know,
  497. eventually allow them to like add thing or at least, you know,
  498. augment that.
  499. This information that would be,
  500. that would be a great thing to do because I suspect there were people
  501. who have things that are like, okay.
  502. Yeah. Most of this advice is still good, but this thing is not.
  503. Or like I've updated this here or like, you know,
  504. you should contact me about this because things have changed.
  505. Thank you so much.
  506. Yep. Do you use the, um, the resources yourself much now?
  507. I will.
  508. Okay.
  509. I'm curious what people are doing in real life.
  510. You know,
  511. cause you make something like this and it's hard to know like,
  512. what are people really doing out there? You know,
  513. I wasn't aware of these resources, but now,
  514. thanks to this webinar, I'm, I'm aware.
  515. So thank you for organizing it.
  516. Of course.
  517. Because we receive tons of emails.
  518. So, and sometimes I don't even open and just read the title.
  519. So, because there are so many emails and we need to prioritize.
  520. But so these, there was in the title,
  521. in the headline of the email, there was written the new resource center.
  522. I said, okay, interesting.
  523. Little editing advice there. I love it.
  524. Yeah. Other thoughts or questions.
  525. Yeah. Well, if nobody has any other questions or sorry,
  526. Sylvia just saw you unmute. I didn't mean to interrupt you there.
  527. Oh, I was out of curiosity. I was wondering,
  528. so every time you refresh the homepage,
  529. there's a different set of suggestions under the search bar.
  530. And I was curious how those are generated.
  531. It is a list that I made up and they are drawn randomly.
  532. And do you have one you'd like to see added?
  533. We can make a pull request right now.
  534. Yeah.
  535. We just add to it.
  536. I don't have anything particular, I guess, but I do often rely on like,
  537. as far as browsing, sometimes I will look there to see like, oh,
  538. what's this other topic that I know nothing about? And I'll click on it.
  539. Yeah. Yeah.
  540. It was me trying to be cutesy. So if you click this link, Sylvia,
  541. I don't know if you're interested in JavaScript,
  542. but you can see the full list right there.
  543. So I wanted them not to be too long so that it wouldn't wrap the two
  544. lines. Yeah.
  545. I do think that we also have the opportunity to possibly like, you know,
  546. maybe we do something where it's like, um,
  547. all like in the month or two or, you know,
  548. after a conference where it's like one of the canned searches is tip
  549. sheets from night car, this year's night car tip sheets from this year's
  550. IRE conference, whether we could do something like that.
  551. Yeah. I think that would be really useful too. Mm hmm.
  552. Cause so many people ask for the chip sheets like right after the
  553. conference you're looking for. I'm like right after. Yeah.
  554. So the constant annoyance of our staff, I'm sure.
  555. We're like, yeah, we're getting there. We're getting to them.
  556. We got to upload all these things.
  557. Yeah. Steep sheet and the presentations,
  558. or if you can share all the presentation, that would be great.
  559. Yeah. Those will be included in many cases. Right. Cody,
  560. if people had like a PowerPoint deck or whatever.
  561. Oh yeah. And in every case we, we have, uh, you know,
  562. we, we talked a little bit about getting some of the, um,
  563. resources from recent conferences.
  564. So if you go to that list that I posted in a chat,
  565. all of those are eventually going to get loaded into, um,
  566. the resource database plus a bunch more, um,
  567. you know, kind of odds and ends. And then, you know,
  568. figuring out like how, like webinars like this, you know,
  569. we record it. Uh, we usually upload this like to our Vimeo, uh,
  570. account.
  571. Our, our previous, uh, system did not have a concept of like,
  572. you know, an embed code for a video or even just like a link to
  573. something as opposed to like a document.
  574. So this will be a lot more flexible and we'll be able to, um, um,
  575. yeah, anything that the speaker send us plus the audio that we record,
  576. we will upload into this for sure.
  577. Thank you.
  578. Any other thoughts, questions, ideas, bug reports?
  579. So be asked what help will we're looking for? Well, bug reports is a big one.
  580. Feature request is another one. You know,
  581. um, for people who are interested in programming or the kind of library
  582. science of doing this kind of thing.
  583. We'd love to welcome people in. The whole thing is open source software.
  584. Um, and that's not just, uh, to show off.
  585. It's really a desperate plea for help.
  586. And, uh, so, you know, if you also have,
  587. if anybody has time or interest in improving the software,
  588. we'd love to welcome you in.
  589. Um,
  590. if anybody has time or interest in improving the software,
  591. we'd love to welcome you into that.
  592. We're currently have a closed source repo where we're trying to work on
  593. that administrative panel. I mentioned, so the staff can update it.
  594. That isn't open,
  595. but if people are interested in participating in that software project,
  596. I would be happy to welcome them in as collaborators.
  597. Um,
  598. and I also, yeah, I think also another way is like,
  599. because we've been talking about,
  600. and then heard from people about like the aspect of like browsing,
  601. like we have our ideas about that. Obviously, you know, like those,
  602. right? Like not randomly, but the ones that Ben already has put in there,
  603. uh, suggestions, but like if people have ideas for like, okay, well,
  604. if I were going to design like a browser, you know,
  605. like a topic system here, uh, you know, like, what would that encompass?
  606. Like, what should that, what would that look like?
  607. What should that look like? Um, like,
  608. I think the more suggestions and input we have on that,
  609. the better any system that we might come up with is going to be.
  610. And I just, uh, toss in the chat, if you just email,
  611. and this is on the, the, uh, page as well.
  612. If you see an issue, email help at irie.org.
  613. If you have a feature request, that's a great place for it too.
  614. All that eventually gets filtered over into a, you know, kind of a bug,
  615. bug track, bug and feature tracking websites, uh, that we use.
  616. So definitely, uh, please kick the tires and let us know what you think.
  617. Yep.
  618. Also that the AI has already sunned me and, and, uh, made its suggestion
  619. for how to improve the code.
  620. So you can see the link.
  621. I've got the, the pull request is already in, I,
  622. what it's describing as the bug sounds right,
  623. but I kind of want to pull that down to my computer and look at it first
  624. before we send it out to the world.
  625. But, um, I think that's probably a pretty good guess just looking at it.
  626. I probably just made the link Ron.
  627. Or I'd made it one way and then changed how it works and forgot to update it.
  628. The kind of dumb stuff you do when you make websites.
  629. Anybody else?
  630. Final thoughts, questions, discussion.
  631. All right.
  632. Well, um, thank you so much to Derek and Ben for being here today and also
  633. just for all the work y'all have put into this.
  634. It's fantastic.
  635. It's such a huge improvement over what we have.
  636. And thank you all for coming to give your feedback.
  637. Like I said, um, help at ira.org, um,
  638. is going to be your email address if you have any feedback.
  639. Um, otherwise we will see around and we will post a recording of this,
  640. uh, on our website soon.
  641. Thank you everybody.
  642. Thanks for coming.
  643. Thanks for your thoughts.
  644. Yeah.
  645. Yeah.
  646. Thank you.

Downloads

Slides PDF · Recording video · Extracted slide text · Timestamped transcript