Time/Place
Time: 2:00pm ET
Audio Conference:
Join from PC, Mac, Linux, iOS or Android: https://duraspace.zoom.us/j/8128353771
Or iPhone one-tap :
US: +16699006833,,8128353771# or +16468769923,,8128353771#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 876 9923
Canada: +1 647 558 0588
Australia: +61 (0) 2 8015 2088
United Kingdom: +44 (0) 20 3695 0088
Meeting ID: 812 835 3771
International numbers available: https://zoom.us/u/MO73B
Attendees
Agenda/ Notes
Discuss NLM pilot details Next stepsTopic Lead Review pilot guidelines and answer any questions David David All
Notes
Desired Outcomes:
- 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
- Requirements:
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