...

• Danny Bernstein 
• Jared Whiklo 
• Peter Eichman 
• Joshua Westgard
• Doron ShalviLongshou Situ
• Bethany Seeger
• Seth Shaw
• Ben Pennell
• James L Woods
• Esmé Cowles
• Aaron Birkland
  
  
  

Agenda

1. Please indicate interest in the Oxford Common Filesystem Layout interest-group

2. Moving Memento work forward:

   1. Remaining work
      1. creating mementos (partially complete)
         1. https://github.com/fcrepo4/fcrepo4/pull/1262 (

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

            )
      2. getting listing of mementos
         1. FCREPO-2623
      3. getting mementos
         

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

   2. Status of Mohamed Mohideen Abdul Rasheed's in progress PR: (https://github.com/fcrepo4/fcrepo4/pull/1262)
      
      1. Do we need a volunteer to bring this one over the finish line? 
   3. Status of https://github.com/fcrepo4/fcrepo4/pull/1250:
      1. Support versioning with versioned child ignored
      2. Is there anything that needs to be discussed as a group in order to move this one forward? (Longshou Situ)
   4. PR's to be merged
      1. https://github.com/fcrepo4/fcrepo4/pull/1261 (

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

         )
      2. https://github.com/fcrepo4/fcrepo4/pull/1260 (

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

         )'
      3. https://github.com/fcrepo4/fcrepo4/pull/1241 (just needs to be merged - all feedback it complete)

3. Follow-up discussion from last week: 

   1. Status of Doran's write-up regarding Fedora's strategy for permalinks
   2. Abandoning the single subject restriction: any feedback/illuminating discussion on the list?
4. Future of fcrepo-audit? - 

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

5. Tickets requiring attention

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

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

       - Peter Eichman is on it

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

       - waiting on feedback from Chris Colvard

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

       - ready to go? Danny Bernstein?

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

       - ready to go? Danny Bernstein?
6. ...

7. Tickets In-Review

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

   
   
   

...

1. 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

   
   

2. 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

   
   

3. 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

   
   

Minutes

Oxford Common File system interest group

We are talking about having a common format for serializing data to and reading serialized data from. This effort does not need to be tied to Fedora efforts.  This seems like it would apply to all repository applications.    We want to be able to dump the contents of the repository that is a complete representation of the repository and then to be able to read in the content.  The effort then is to define a common way for this data to appear/be organized on disk.

Fedora could support anything coming out of this interest group, but would not be a Fedora initiative.  Fedora could provide tooling to support this in Fedora.

Possibly some interest from the folks at UCSD?   Esmé Cowles will discuss with colleagues / associates at Princeton.  Declan Fleming might be interested? 

This doesn’t seem to be a developer interest group, but perhaps should be discussed at a more administrative level.

How to move the memento /  API-alignment effort forward?

One challenge is that there is not so much opportunity for parallelizing the work.

Jared Whiklo will pick up Mohamed Mohideen Abdul Rasheed’s PR if Danny Bernstein hasn’t started it.

Call for developers to work remaining tickets OR at least review 

Jared Whiklo on point for pushing through memento work

Sprint for early 2018? 

Actions

•  Danny Bernstein will try to push forward on FCREPO-1262.
•  Doron Shalvi will write up a description of the Fedora URI concerns and post to the Fedora listserv to start discussion.
•  Peter Eichman will create a ticket to document the stuck thread issue that UMD experienced and how they have resolved it thus far. https://jira.duraspace.org/browse/FCREPO-2648