...
Attendees
- Danny Bernstein
- Esmé Cowles
- Ben Pennell
- Michael Durbin
- Peter Eichman
- Joshua Westgard
- Bethany Seeger
- (Please add your name)
Agenda
- Announcements
- 4.7.5 Release Process begins
- 4.7.5 release - Planning for week of January,15th 2018
- Release manager - Osman Din
- Volunteers
- Testers
- Someone to review 4.7.5 commit message for signs of missing documentation?
Preparers of Module Release Candidates
Module Who? fcrepo-module-auth-rbacl fcrepo-module-auth-xacml fcrepo-module-auth-webac fcrepo-mint fcrepo-audit fcrepo-webapp-plus fcrepo4-vagrant
- Resources:
- component release process tracker: https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
- Release Testing - 4.7.5
- 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>}
- Tickets requiring attention
- Bethany Seeger to review?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2520
- 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
- on hold or close?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2544
- 5.0.0 release
- API Alignment
- Pairtrees?
- Danny Bernstein working this?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2617 - Is tying Memento creation to modeshape a bad idea?
https://github.com/whikloj/fcrepo4/blob/fcrepo-2617/fcrepo-kernel-modeshape/src/main/java/org/fcrepo/kernel/modeshape/services/VersionServiceImpl.java#L72
- Is tying Memento creation to modeshape a bad idea?
- Daniel Lamb working this?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2632
- 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
Danny B will be hosting next week's call
...
- OCFL call
- round robin survey of digital preservation at 6 institutions
- application independent disk/fs layouts
- [Danny B] key takeaways?
- covered tooling/specifications for standardizing file storage layouts
- effort from Stanford called "Moab" to group these tools, adds process as a layer on top, does versioning
- looking for common elements across institutions' digital preservation file storage strategies
- [Bethany] more "what are we doing" conversations useful
- [Bethany] what about distributed setups for serving the data?
- assume we are writing to disk
- "disk" is not fully specified
- scale wrt lots of content but not performance issues
- 1.b. think about using Slack more on the technical side of Fedora?
...
- [Carrick] it is on DevOps TODO list, should happen in the next 2 weeks (11-22 Dec)
...
- aim to get a RC out soon (this week or next)
- [Danny B] will review master on Monday for bugfixes that should be backported, cherrypick onto 4.7-maintenance
- do release off 4.7-maintenance branch
- look for unresolved bugfix tickets
- [Peter] can do RC testing first week of January
- [Carrick] can also RC testing first week of January, w/Avalon & Hyrax
- [Danny B] will put out RC next week
- [Jared] will assist
- will likely have to push out the Jan 15 release date
- review tickets for anything you want in 4.7.5 that is not yet
...
- [Doron] we hold DC Fedora Users Group twice a year
- had a smaller meeting at UMD to focus on architecture needs, upcoming needs, and a discussion of community status
- attendees: Doron, Esmé, Josh Westgard, Peter, Mohamed, Ben Wallberg
- NLM is just beginnning additional projects that require architecture buildout of enduser admin tools
- currently on F3, want to migrate, ran into issues before
- discussed Hyrax, Figgy, Valkyrie
- IR vs. digital repository, CMS-like feature that we don't need
- current model is to have large files on fs, external links in F3, would like to continue this model in F4
- would like F4 to support the "rebuild repo from fs" capability that OCFL promises
- NLM thinks F4 conceptually seems fine for modelling
- performance is still an issue in migration
- [Aaron B] F4 is more akin to a resource store rather than an object store
- provides primitives to model objects
- resources are managed and versioned individually
- OCFL defining object repo in the filesystem
- resembles the F3 object notion
- F4 provides tools to model objects, but not persisted and managed as a unit
- OCFL object members are collocated in some structure
- can F4 provide guidance on structuring resources in the userspace level?
- [Doron] looking for F4 to provide an object store
- want to publish RDF on the web
- fine with using multiple tools for object store and object publishing
- [Andrew] reflect on the API spec and imagine if your achitecture can use it
- related to the question of what services should Fedora offer
- not ideologically bound to the single subject restriction
- [Doron] where should LDP functionality live in the stack
- Fedora is not a triplestore, its an object store
- [Aaron B] "object store" is not defined anywhere
- F4 API describes resources, not objects
- objects is a high-level concept that is constructed through relationships
- left as an exercise for the user to define objects in terms a of linked data
- [Peter] F3 had built in object model
- need to start object model sharing and reuse discussion?
- [Andrew] PCDM was the first attempt at object model consensus
- [Aaron B] F4 not opinionated wrt object models
- [Andrew] mapping flexibility of resources on F4 to OCFL will be an interesting exercise
...
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.
Action: Esme to write up brief description of proposal to remove pair trees for fedora tech
...