...
Attendees
- Danny Bernstein(Please add your name)
- Randall Embry - Indiana University
- Peter Eichman
- Aaron Birkland
- Esmé Cowles
Agenda
- Star master
- Announcements
- Holiday Party follow up meeting : Monday January 8th at 3PM Eastern
- https://docs.google.com/document/d/10TpyqAVgy110Zph_aYAH-bJIfNZr4Vj1e3-vhTfUv4U/edit#
- Shall we put it out there.
- Holiday Party follow up meeting : Monday January 8th at 3PM Eastern
- 4.7.5 release - Planning for week of January,15th 2018
- Shall we push it out a week?
- Announcement needs to be sent
- Release manager - Osman Din ? Need confirmation Danny Bernstein
- Volunteers
- Testers
- Someone to review 4.7.5 commit message for signs of missing documentation?
Preparers of Module Release Candidates
Osman DinModule Who? fcrepo-module-auth-rbacl
Osman Dinfcrepo-module-auth-xacml
Osman Dinfcrepo-module-auth-webac
Osman Dinfcrepo-mint
Osman Dinfcrepo-audit
Osman Dinfcrepo-webapp-plus
Osman Dinfcrepo4-vagrant
- Resources:
- component release process tracker: https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
- Release Testing - 4.7.5
- Shall we push it out a week?
- Fedora API Test Suite... needing:
- Try the tool against an API implementation
- Code reviewing the tool... lots of low-hanging fruit
- Simple, synchronous query in Fedora
- What will it take to make this happen?
- Prior art
- Queries to support
- select ?s where {?s ?p ?o}
- select ?s where {?s <some-pred> ?o}
- select ?s where {?s <some-pred> <some-object>}
- Michael Durbin: do we have a link to the document tracking known limitations of modeshape implementation and requirements?
- Tickets requiring attention
- Bethany SeegerJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2520 - Any more discussion needed here? If a mimetype goes in, it should come out at the very least.
- 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
- Ralf Claussnitzer: Sounds reasonable. HTTP servers should respond with BAD REQUEST if given an unparsable mime type string. Should the repository layer check again?
- Ralf Claussnitzer to explore?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2659
- Ben Pennell to explore?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2650
- 5.0.0 release
- API Alignment
- Pairtrees?
- Esmé Cowles : status of proposal and/or any feedback from community?
- Beyond 5.0.0 - Areas of improvement
- Persistence?
- Journaling?
- Simple, synchronous query?
- ...
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
...
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 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 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
- Needed queries
- 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
- Discuss some of the known limitations of modeshape's internal indices
- 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.
...
- There will be a Fedora Committers meeting next week
- Fedora 4.7.5 release
- Osman will not be able to be the release manager, so Danny Bernstein will be the release manager
- The release will be delayed a week or two
- Fedora API test suite
- Outside developer working on a test compatibility kit for verifying whether an implementation implements the Fedora API spec
- Lots of opportunities for code review and helping
- Synchronous Query
- Document for tracking known limitations of Modeshape implementation for query
- 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
- Ticket review
- 2520: have reached general agreement here
- API alignment and Fedora 5.0
- Danny will work on Memento generation next week
- AppleTrees: not a ton of feedback, but generally not in favor
- Randall: Don't want to discourage progress, and 5.0 seems like a good place to integrate new breaking features
- But we don't see a lot of benefit from shortening URIs, and would rather avoid data migration issues
- Peter: Andrew suggested we could make the default minter config flatter, but document configuration options for PairTrees or AppleTrees, etc. for performance
- Aaron: PairTrees partition the repository with containment relationships that are different from most other containment relationships, longer URIs aren't the main issue
- 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
- Paging or other approaches might work
- Randall: Don't want to discourage progress, and 5.0 seems like a good place to integrate new breaking features
- We should assess the impact of making changes, and how disruptive they might be
- 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.