...

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

4. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Notes

1. Announcements
   1. David Wilcox  mentioned a grant that's being applied for to IMLS.  Currently working on a full proposal that would be a follow on grant to the migration grant from last year. Looking for institutions to work with (as a pilot). Contact David if interested.  Goal is to proof out fedora 6 and build a bunch of documentation / training to create more of a path for migration for the community at large.  https://drive.google.com/file/d/1vbgn_OWChV1u6oYdzQ3-yT4Chwv0nmgc/view?usp=sharing

      1. Will grant consider Fedora 3 → OCFL (outside of Fedora)?  Some might use the migration to get to OCFL w/ or w/o Fedora. Work will be valuable to anyone going to OCFL in general.    Would be good to know if Fedora3 users who are interested in a more generic OCFL migration tool that's not Fedora specific.  The migration tool does create generic OCFL - it be good to make sure the Fedora code that rebuilds the index from OCFL doesn't depend on .fcrepo directory.   Feasibility? Feasible, but a slightly different start point - one with fedora data (.fcrepo) and one with out.  Right now they are planning on .fcrepo being there, so it'd be a shift.  There would have to be some assumptions made to read that OCFL data. Would be good to infer different characteristics from generic OCFL.
      2.  A stand alone tool would be useful, as it might be really hard w/o input for Fedora to reason over data. Concern is if we load the generic OCFL data wrong, you can't change the interaction model. Maybe some sort of migration tool that looks through the data, that catches issues and asks users, but that could be tedious.  Maybe build up a decision tree for their data, so user can have some input. Build some sort of reasoning over a corpus of OCFL data.  Find a way to tell fedora how to do it's decision making over the users data. 
      3. There is the migration tool that takes F3 → Generic OCFL.   We could use this output to test out what issues Fedora 6 falls into when rebuilding from that OCFL to get a better sense of what the issues we might run into are.
   2. First combined Islandora 8 / Fedora camp next week at ASU (Feb 24 - 26). 
2. Fedora Demo
   1. Auto-versioning is working - it's a switch you can run with. `-Dfcrepo.autoversioning.enabled=true`
   2. Should take about 5 minutes and should have enough content
3. Backwards compatibility document
   1. Immutable ghost-nodes
4. Road to Fedora 6
   1. Milestone list
   2. Getting sprint dates on the calendar
5. Priority tasks (Development Roadmap : 2020 Sprint Roadmap)

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3232

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3216

6. To review:

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3195

7. <your topic here>

Actions

•  Clarify in in documentation that multiple simultaneous writes to OCFL are not supported

...