Versions Compared

Old Version 3

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user Danny Bernstein

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees 

Agenda

  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?  
      1. Announcement needs to be sent
    2. Release manager - Osman Din ? Need confirmation Danny Bernstein
    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

        ModuleWho?
        fcrepo-module-auth-rbacl
        Osman Din
        Danny Bernstein


        fcrepo-module-auth-xacml
        Osman Din

        Danny Bernstein

        fcrepo-module-auth-webac
        Osman Din

        Danny Bernstein

        fcrepo-mint
        Osman Din

        Danny Bernstein

        fcrepo-audit
        Osman Din

        Danny Bernstein

        fcrepo-webapp-plus
        Osman Din

        Danny Bernstein

        fcrepo4-vagrant
        Osman Din

        Danny Bernstein


    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
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2520
      - Bethany Seeger
      1. Any more discussion needed here?  If a mimetype goes in, it should come out at the very least. 
      2. Bethany Seeger suggested an alternative implementation: https://github.com/fcrepo4/fcrepo4/pull/1272#issuecomment-353173508 that would move the check closer to the HTTP layer
      3. Ralf Claussnitzer: Sounds reasonable. HTTP servers should respond with BAD REQUEST if given an unparsable mime type string.  Should the repository layer check again?
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2659
      - Ralf Claussnitzer to explore?
    3. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-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
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=14307
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


...

  1. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets created this week:

    Expand
    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-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.

...

  1. There will be a Fedora Committers meeting next week
  2. Fedora 4.7.5 release
    1. Osman will not be able to be the release manager, so Danny Bernstein will be the release manager
    2. The release will be delayed a week or two
  3. Fedora API test suite
    1. Outside developer working on a test compatibility kit for verifying whether an implementation implements the Fedora API spec
    2. Lots of opportunities for code review and helping
  4. Synchronous Query
    1. Document for tracking known limitations of Modeshape implementation for query
    2. There was a query service at one point, but it was removed because of complications of LDP container implementation with dynamic triple generation, and lack of testing/verification
  5. Ticket review
    1. 2520: have reached general agreement here
  6. API alignment and Fedora 5.0
    1. Danny will work on Memento generation next week
    2. AppleTrees: not a ton of feedback, but generally not in favor
      1. Randall: Don't want to discourage progress, and 5.0 seems like a good place to integrate new breaking features
        1. But we don't see a lot of benefit from shortening URIs, and would rather avoid data migration issues
      2. Peter: Andrew suggested we could make the default minter config flatter, but document configuration options for PairTrees or AppleTrees, etc. for performance
      3. Aaron: PairTrees partition the repository with containment relationships that are different from most other containment relationships, longer URIs aren't the main issue
      4. Peter: we used the partitioning to make it easier to list all objects in the repository node-at-a-time when getting timeouts trying to list all at once
        1. Paging or other approaches might work
    3. We should assess the impact of making changes, and how disruptive they might be
    4. Esme: With the versioning implementation changes coming in 5.0, we may be able to revisit some of the identifer-translation changes that Benjamin Armintor and Unknown User (acoburn) explored, and we may be able to address the underlying performance issues that lead to PairTrees and other approaches.