...
- Success would mean Fedora6 is something we can use and the steps for migration would be clear
- Something we can use:
- Requirements:
- Migration performance
- how many objects representing
- how much data migrated in
- how much time
- Migration performance
- Are the development targets outlined by the Fedora 6 design summary aligned with NLM's needs?
- Concern around external content
- Current F3 stack makes heavy use of external content
- How to use an external content model with the Fedora6 / OCFL design?
- Would we (NLM) have to bring in all the external binaries into Fedora ? Or is would it make sense to use external content?
- OCFL objects can point to external content (via a URI)
- NLM would always have the option to bring in the content into OCFL later.
- Having binaries and metadata collocated is a principle of OCFL not a requirement
- Concerns around RDF and LDP:
- NLM wants to use own URI's for subjects.
- Other concerns detailed in this discussion: http://fedora-commons.1317035.n2.nabble.com/fedora-community-URLs-as-URIs-for-digital-objects-td7585842.html
- The issue is close to the heart of the metadata community
- Requirements:
Timelines / Responsibilities
- Two sprints for fedora - September and November
- We're looking at year long road map with Fedora 6 + migration tooling
- Aiming to wrap up the pilot around this time next year.
- Does that timeline seem reasonable to NLM?
- Busy through September
- Overall timeframe looks good
- Sample data:
- Andrew Woods is moving migration-utils project forward insofar as it is writing to OCFL directly
- It would be helpful to vet the performance characteristics of that migration approach.
- Having a Fedora3 tar file would be useful for us to run some tests in the short term.
- One initial test would be to run migration utils without writing anything on the fedora to establish a baseline for performance.
- 60 TBs and 10 million objects
- How important is it to retain your own URIs?
- Currently permalinks are stored in the object metadata
- NLM does not care so much that Fedora 3 URLs change in the migration.
- Fedora URLs are used in NLMs architecture so changing the code that resolves fedora links will have to change, but that is not a big deal.
Communication:
- As sprints kick-off the Fedora team will need feedback on progress.
- NLM's participation in the weekly tech calls and #fedora6-pilot would be very helpful.
Actions
- Danny Bernstein to bring in the question of external binaries in OCFL in the weekly tech call. Pilot partners should feel free to raise the issue on in the #fedora6-pilots slack channel
- Andrew Woods to schedule a dedicated call to discuss URLs as URIs for digital objects.
- Nancy Fallgren and everyone in the current meeting to review the thread and make sure to raise any issues that are not touched on in the thread.
- Andrew Woods to work with Doron Shalvi on determining the way forward re sample data