...
- Announcements:
- 2024 Virtual Fedora Showcase announcement - Oct 1-3, 2024 online
- Toying with the idea of a workshop in advance of the meeting (maybe 2 hrs on Day 1)
- Conferences
- iPres - late Sept in Ghent, Belgium
- Access 2024 - late October in Montreal, QC
- 2024 Virtual Fedora Showcase announcement - Oct 1-3, 2024 online
- Pop-up/Other Topics:
- David Novak's reindexing issue
- Slack Issue - https://fedora-project.slack.com/archives/C8B5TSR4J/p1720542366141449
- Customizing ACL's
- Slack Issue from Islandora - https://islandora.slack.com/archives/C019U12D44Q/p1720699950434699
- Context: "Non fedora files" (according to the non_fedora_files view) are all files in the site where the url schema doesn't start with "fedora://". They can be indexed in Fedora, though, so that if you have "Media standalone urls" turned on, the media page shows a Fedora URL and that Fedora URL redirects you to the file. I believe this uses a "external content" feature of Fedora.But I'm surprised that [fedora url]/fcr:metadata doesn't result in any metadata. Normally the contents of the Media (as mapped into jsonld) are present at [fedora file url]/fcr:metadata. This normally includes the node title, the creation date, the height and width, etc.Is there a bug in the way we're storing external content, or does that fcr:metadata path just not work in Fedora for External Content? Also, there's an Action to delete (node|taxonomy term|external_file) from Fedora, but not delete media from fedora. Was that intentional?"
- Migration Updates:
- Updates on:
...