...

• Review of Pilot objectives
• Desired outcomes?
  • Data model would change when migrating to Fedora 6 in all probability
  • Will have specific needs for the data migration
  •  DT is considering moving to a linked data 
    • there is a  proposed mapping  - Thomas will need to dig it up
  • Clear picture of how they will migrate to Fedora 6
  • Clear picture of what it will take in terms of time and resources  to migrate
  • Clear picture of how to deploy Fedora 6
  • Specific performance requirements:  not clear what will be necessary
  • Size: 100 GB binary - 5 TBs of binaries
  • What is object count range across instances? * 
  • Ingest and retrieval speeds?  Data / Object count  per second 
  • 50 fedora installations
  • Objectives related to surrounding processes or front-ends:
    • will be using some kind of index
    • will be using a triplestore
    • currently using CRUD functionality
    •  what are the queries you expect to be supported? *
• Timelines:
  • Starting in September
• Our expectation is that we'll be able to get feedback on alpha / beta releases
• Communication
  • We will provide regular (weekly? bi-weekly) check-ins for pilot partners
  • meeting at 11 am eastern would be ideal
  • Slack channel:  #fedora6-pilots
• Is Docuteam available for development work? 
  • Testing yes - unquestionably
  • Development:  we don't know - looking at outsourcing development.
  • May be able to contribute to migration libraries.
• Providing sample data to the Lyrasis/Fedora team ASAP would be appreciated.
  • DT has about 20 sample objects that are based on their objects that they can provide.
    • DT:  look for it in the second week of August.

Use cases and requirements

Query service

Use cases

Requirements

• should work like a SPARQL endpoint
• if integrated into fedora: make optional
• possibility to query persistence layer for used storage and free storage

Questions

• will query service be part of the fedora API spec?
• does it make sense to hardcode the supported queries?
• use a real SPARQL endpoint in the background? only deliver a UI?

Persistence

Use cases

• OCFL: native support to use s3 compatible object storage
• alternative “simple” persistence implementation

Migration

Use cases

• We the switch to Fedora6, docuteam wants to switch to a ontology-based data model.
• Docuteam would like to leverage the functionality of a generic migration utility.

Requirements

• possibility to select/configure which Fedora3 datastreams should be converted to Fedora6 binaries
• possibility to extent migration utilities with custom parsers/functionality to create triples

Documentation

Requirements

• Step by step installation manual for production use
• Recommendations for storage systems (e.g. WORM, Object Storage, generic NAS)

Communication channels:

• fedora-project.slack.com:
• wiki
• #fedora6-pilots
• #fedora-tech
• fedora-tech@googlegroups.com
• fedora-community@googlegroups.com

Actions

•  Thomas Bernhart  to deliver sample data  to Andrew Woods by August 16th.

...

•  Thomas Bernhart  to deliver use cases, and requirements to Andrew Woods by September 6th.