...
- Announcements
- Leaders and Committers On How to Encourage Fedora Users to Register
- Why the registry is important
- The state of the registry now
- What can we do?
- In the UI
- on the Command line
- On our ecosystem projects (camel toolbox, migration utils, etc)
- Islandora
- Samvera
- NLM Migration Update
- New Tickets
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3811 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3812
- New Tickets
- 6.2.0 Release
- PRs that need to be resolved
- Jira, Slack, Github integrations
...
How would we get information about Fedora's that are part of a prefab tech stack?
- Samvera
- Islandora
Bring To bring the tech team to this problem is vital.
We have an existential threat to our project because we don't know have data: we are not creating spyware, we are trying to help our community.
From Jakov:
OJS has a beacon feature which we might consider replicating in Fedora
- Has an opt out - perhaps we should consider opt in
- generate unique id
- send information to Fedora
- What information:
- Fedora Version
- IP
- Institution
- Country
- Contact Email
- Periodically send stats (object count, byte count)
- What information:
Provide ability to offer different levels of information
Possibly remind folks when they upgrade the software?
What data does not present risk?
Scott's Notes:
Many Fedora 3's have been inherited from the original implementers by IT groups, digital archivists and collections managers who may not be plugged into the community via email lists, etc.
- So I'd recommend an outreach effort that focused on publicizing Fedora 6 and migration help outside the usual channels
- posting to forums like code4lib, the dspace forum (many institutions that run DSpace also run Fedora), NDSA lists, PASIG lists, Samvera, Islandora, etc
- Digital curation listserv as well