...
Time | Topic | Presenter | |
|---|---|---|---|
| 10:00 - 10:30 | Welcome coffee and introductions | All | |
| 10:30 - 11:00 | Institutional updates round (One person from each institution in attendance will be asked to give a short overview of work going on at their institution, particularly work not covered in longer presentations.) | All | |
| 11:00 - 11:30 | Master storage in AWS Glacier | Doron Shalvi, Calvin Xu | |
| 11:30 - 12:00 | NASA Goddard Library migration update | Adrienne Hieb, Matt Pearson, Mitchell Shelton | |
| 12:00 - 1:30 | Lunch | ||
| 1:30 - 2:00 | API Alignment Sprint Update | Joshua Westgard | |
| 2:00 - 2:30 | 2:30 - 3:00 | Maryland Student Newspapers Demo | Ben Wallberg |
| 32:00 30 - 32:1545 | Break | ||
| 32:15 45 - 3:3015 | A Python-based bulkload client for the Fedora REST API: Some techniques, best practices, and lessons learned. | Joshua Westgard | |
| 3:30 15 - 3:45 | OCR Text as Web Annotations | Peter Eichman | |
| 3:45 - 4:00 | Wrap up & discussion | All |
...
Time | Topic | Facilitator(s) |
|---|---|---|
10:00 - 10:15 | Welcome & coffee | All |
| 10:15 - 12:00 | Demos/Discussion:
| John Rees TBDJoshua Westgard |
| 12:00 - 1:00 | Lunch | |
| 1:00 - 2:45 | Tour of Goddard Facilities | Matthew Pearson |
| 2:45 - 3:00 | Break/Transition | |
| 3:00 - 4:00 | Wrap-up Roundtable | All |
Takeaways and Action Items
- Concerns were raised about the way the current implementation exposes the path to files as the RDF subject rather than an opaque identifier-based URI. It was agreed that the follow-up conversation should be brought to the wider community.
- Future meetings will be organized by a committee, initially consisting of representatives from the four institutions in attendance at this meeting (NLM, NASA, NAL, UMD).
- Goals for future meetings are to further expand the active participation of local LAM institutions who are either using or interested in Fedora.
- Some ideas for future meeting programs:
- Training/workshops on specific related technologies, such as Samvera, Islandora, IIIf, etc.
- Perhaps a "Fedora 101" training would be useful for attracting non-users interested in exploring what Fedora is
- Explore aligning FUG meetings with other local meetings as a way to increase attendance (CNI?)
- Try to advertise more thoroughly and widely
- Explore connecting with other FUGs (either a nationwide "virtual connect" type meeting, or perhaps a physical meetup with the Mid-Atlantic FUG – possibly with Baltimore as the meeting place)
- The presence of a Duraspace rep at the meeting is desireable and should be maintained if possible going forward.
- We should look to create a presence for Fedora and the FUG at the upcoming C4L in Washington – though it is probably too late to get formally on the program, we should seek out ways to create some presence for the FUG there.