View Source

Regular Attendees

Andrew
Bill
Brad
Chris
Dan
Jonathan

General

Call In To: Free Conference Call HD - DuraCloud Line
Please note that we will be using the Free Conference Call HD line for this call. Information about calling into this line is available from the link above.
- Indicates who will be taking minutes

Discussion Topics

Planning Board
Task Board
DfR Planning and Estimating - 0.1

Topic	Discussion Leader
Planning and Task Boards - Review and Building the Backlog	Dan
Conceptualizing/Design Synch Tooling	Dan
Project and Partners	Jonathan

Actions from last meeting

Last meeting

Last Weeks Actions:

Action Item	Assignee	Status

Write Cards for Updates to Support OCS - Add on Tasks for Iteration 1	Chris
Determine key pipeline tools to demo (characterization), Connect to FITS or others	Dan and Jonathan
Rephrase DfR 1 to better fit future iterations	Dan
Rephrase DfR 74 wrt Fedora	Dan and Chris
Better conceptualize accounts for DfR	Team	Postponed
Conceptualizing/Design Synch Tooling	Bill
Better set the feasible scope for this year in automated metadata collection	Team
Connect to Paul Pound on Islandora	Dan

Status

Jonathan
Andrew
Bill
- In progress: DFR-74.
  - First step, creating wrapper DuraBoss application is complete
  - Bit integrity service handler is in process.
Brad
Chris
Dan
Jonathan

Minutes

review of last week's meeting
1. conceptualizing sync tool
2. want to pick out a few things we want to show
  - can currently push files to DuraCloud
  - need to be able to make this more usable/useful to the user
  - need to be able to build good Fedora objects (OCS)
3. how to make Fedora objects richer
  - characterization: customizable pipeline
  - format identification, can create tooling if we know more than mime of an item
  - extracting geo-location info
trying to define the picture of what we will be able to demonstrate
- demonstrate content characterization
- would like to associate metadata on client-side with various directories
fedora objects rendered in SI UI
- key question: when do people input extra metadata
  - on client-side?
  - after content is exposed in SI?
  - where does it make sense for format identification to happen?
OCS as a general pipeline
- can be entered from SI UI as well as from the sync tooling
we need some stories for demonstration scenarios
- file characterization (tie-in pronom)
- client-side association of metadata with directories
- demo end-to-end flow of content
  - capture relationships of directories and items for rendering collections
  - show project organization
  - show filesystem view
Dan to get a virtual machine from Paul Pound
need to work out issues of authN/authZ with SI and underlying DfR
- enable an embargo capability
- access control
certain people/roles have certain capabilities
- need to enforce policies around those roles
- fedora to use the primitives in DuraCloud, but go beyond them
  - env attributes, resource-oriented attributes, etc
stories
- use characterization tools to mark up objects with mimetype
- use characterization tools to mark up objects with format-id beyond mimetype
example
- extracting metadata from photos
  - time
  - camera info
  - geo-location?
implementation
- when do we augment fedora objects?
- what is the responsibility of the OCS?
  - simply adding original content into fedora?
  - additional characterization happens later, and references the original objects
- considering a firm technical distinction from object creation & object characterization/enrichment
need to add new demo stories to jira