Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
- Jared Whiklo
- Peter Eichman
- Andrew Woods
- Carrick Rogers
- Bethany Seeger
- Aaron Birkland
- Yinlin Chen
- Seth Shaw
- Danny Bernstein
- Doron Shalvi
- Ben Pennell
Agenda
- Announcements
- Oxford Common Filesystem Layout meeting happened last Friday
- Auto-invite form for fedora-project slack now available (thanks Michael B. Klein)
- Needing volunteers
- 4.7.5 release - Planning for week of January,15th 2018
- Release manager - Osman Din
- 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
- 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? -
- Ralf Claussnitzer to explore? -
- Ben Pennell to explore? -
- - on hold or close?
- 5.0.0 release
- API Alignment
- Pairtrees?
- Danny Bernstein working this?
- 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? -
- Beyond 5.0.0 - Areas of improvement
- Persistence?
- Journaling?
- Simple, synchronous query?
- ...
Tickets In-Review
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
Danny B will be hosting next week's call
- OCFL
- 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?
- OCFL call
- Clustering config
- [Carrick] it is on DevOps TODO list, should happen in the next 2 weeks (11-22 Dec)
- 4.7.5 release, scheduled Jan 15
- 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
- UMD/NLM achitecture meetup
- [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
- encourage folks to run API test suite at various implementations
- desire for very simple synchronous query in F4
- [Jared] are we putting query into F4?
- [Andrew] this is just exploratory for now