Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
Attendee
Agenda
- Progress Report on Fcrepo-Cloud-Migrator Tool
- Message emission in for inbound link targets.
-
- Review Spec committee's direction on Fedora API Specification github issue (one-step fixity check)
- Also what about dangling question about storing checksums as a server managed triple?
- Sprint doodle poll results: https://doodle.com/poll/2vgw3huvr8dugeuq: emerging consensus
- Sept 10-24
- Oct 1-14
- OR:
- Dinner Meetup?
- T-Shirts
- Intro Workshop
- Talks you're giving, talks you're excited about?
- Getting to 5.0
- Review of work that happened this week:
- External content (proxy, copy, and redirect) - PR merged, there are a few issues relating to it that are low hanging fruit.
- 5.x Documentation Effort
- 5.x Documentation Updates matrix
- Ecosystem tools progress report
- import export tool
- camel tool kit
- fcrepo4-vagrant
- java client
- api-x
- Progress Report on Fcrepo-Cloud-Migrator Tool
- variants in .ttl between the python export and ruby-rdf
- Reviving OAI Support
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
Actions
- Look at fcr:fixity in JIRA - creating a ticket and look at options
- See if possible option for fixity checking could be an API-X service
- Talk to API Spec group about returning fixity check result as an additional header, returned on 'want-digest'.
- Peter Eichman - See how tightly bound our current implementation is to modeshape, in regards to the fixity endpoint. Can look at at the end of next week.
- Message to list-serve to see who might be using fcrepo-java-client outside of fcrepo-camel
- Jared Whiklo - New JIRA ticket to explore nature of changes before messages are emitted
- Andrew Woods - Send out a Doodle poll to get a timeframe for next 5.0 sprints (July-October dates)