Page History

...

1. Star master
2. Announcements
   1. Holiday Party follow up meeting :  Monday January 8th at 3PM Eastern 
      
      1. https://docs.google.com/document/d/10TpyqAVgy110Zph_aYAH-bJIfNZr4Vj1e3-vhTfUv4U/edit#
      2. Shall we put it out there.
3. 4.7.5 release - Planning for week of January,15th 2018
   1. Shall we push it out a week?  
   2. Release manager - Osman Din ? Need confirmation
   3. Volunteers
      1. Testers
         1. Danny Bernstein
         2. Joshua Westgard
         3. Peter Eichman
         4. ?
      2. Someone to review 4.7.5 commit message for signs of missing documentation?

      3. Preparers of Module Release Candidates

         Module	Who?
         fcrepo-module-auth-rbacl	Osman Din
         fcrepo-module-auth-xacml	Osman Din
         fcrepo-module-auth-webac	Osman Din
         fcrepo-mint	Osman Din
         fcrepo-audit	Osman Din
         fcrepo-webapp-plus	Osman Din
         fcrepo4-vagrant	Osman Din

         
         

   4. Resources:
      1. component release process tracker: https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
      2. Release Testing - 4.7.5
4. Fedora API Test Suite... needing:
   
   1. Try the tool against an API implementation
   2. Code reviewing the tool... lots of low-hanging fruit
5. Simple, synchronous query in Fedora
   1. What will it take to make this happen?
   2. Prior art
   3. Queries to support
      1. select ?s where {?s ?p ?o}
      2. select ?s where {?s <some-pred> ?o}
      3. select ?s where {?s <some-pred> <some-object>}
   4. Michael Durbin:  do we have a link to the document tracking  known limitations of modeshape implementation and requirements?
6. Tickets requiring attention

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

      - Bethany Seeger
      1. Any more discussion needed here?  If a mimetype goes in, it should come out at the very least. 
      2. ?

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

      - Ralf Claussnitzer to explore?

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

      - Ben Pennell to explore?
      
      
7. 5.0.0 release
   1. API Alignment
   2. Pairtrees?
      1. Esmé Cowles : status of proposal and/or any feedback from community? 
8. Beyond 5.0.0 - Areas of improvement
   
   1. Persistence?
   2. Journaling?
   3. Simple, synchronous query?
9. ...

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

2. Release

• Esme can help with Samvera testing
• Osman will perform builds of module release candidates, unless he wishes to delegate
• May be a challenging release given holidays

3. API test suite been running for a while. Has anyone had a chance to look at it?

• Danny hasn't looked at it yet, but seems easy to use. Going to try it out this week
• Interested in people trying it against other implementations, like Trellis and Cavendish.
• Bethany: Is this considered done as far as the contractors are concerned?
  • Danny: Good question, the repo doesn't say how complete it is. Will check in with Andrew
  • Since the API alignment isn't complete, it shouldn't pass against modeshape impl yet
  • Code reviewing the tool?

4. Simple querying in Fedora?

• Previously, cbeer had added this functionality, but it had been later removed
• Is data structured for this in modeshape to be reasonably performant?
• Mike: Was one of the agitators for this, opposed it being cut
  • Some stuff is inferred, some not directly searchable
  • What types of queries do we want to support?
  • What exceptions are we willing to tolerate?
  • Extension spec?
  • Is it okay if it doesn't work consistently on server managed triples, like date fields?
  • Just wants to be able to search dc:identifier. This would work, modeshape has an index that can be searched.
• Esme: Valkyie, making a list of queries that the repository needed.
  • Needed queries
    • all objects of given type
    • Doing a search for dc:identifiers
    • They will come up with a list of queries they need
• Danny: Would it be helpful at this point to fill out the list
  • Discuss some of the known limitations of modeshape's internal indices
    • Mike: Last modified date is across two fields. Might need to normalize way stored in fedora. Need to work out if this is needed
    • Esme: Types and containment triples are harder to make searchable
    • Search for non-server managed triples that are directly assigned are easy.
    • RDF type are not stored in the index modeshape maintains. That is inserted into responses.
    • Use case: find all objects of a type in order to do bulk object on it
    • Can't search on fcr namespace and ldp namespace. Might be okay to not support those, but it would be weird to have an LDP server that didn't support it
    • Could add support for this in after if there is demand for it
• Mike will start document to gather first pass at known limitations of implementation and requirements

5. Tickets requiring attention

• 2520
  • Bethany would like more feedback on what expectations are for mimetype
  • She will take another look at it to try to work through what the validation issue is
• 2650
  • Bethany will take a look
• 2544
  • there was a work around for that, using a different accept type. No one has strong feelings that it shouldn't be closed, so will make a note on ticket
  • Josh - as a larger strategy, this is something we will need to address
  • Paging mechanism is problematic in RDF rest api, but something we will need to deal with
  • Work around okay for now, but many members issue needs to be addressed in future implementations

6. 5.0.0 release?

• Need to wrap up creation of mementos, one of the last main things to bring into alignment with spec
• Pairtrees - Do we want to remove them?
  • Peter (?): In favor of removing them
  • Significant bit of internal work to hide them at fedora level, while still might need them in jcr
  • Danny: In doing away with pair trees, they would still be around internally
  • Peter: Need them, otherwise performance tanks after about 1000 children
  • Esme: Might want to look at Aaron Coburn's Appletree implementation. Takes checksum, makes path based on that. Includes hiding internal paths
  • Esme: would involve renaming everything in your repository, so it would need to take place as part of a major version change
  • Esme: Would either need migration tooling, or tooling for enabling/disabling the feature
  • Danny: how hard would a migration tool be to created?
    • Esme: Would be complex, but possible. If you have been using auto-generated UUIDS, could go through repo and remove pairtree.
  • Danny: interesting proposal, do we need community feedback?
    • Yes, more feedback would be good.
    • Esme: to write up brief description of proposal for fedora-tech
    • For discussion in new year

Action Items

Action: Check in with Andrew about completeness of the test suite

Action: Mike will put together a document with first pass at the feature set.

...