Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

Attendees

Part 1: 

  1. Danny Bernstein 
  2. Peter Winckles 
  3. Jared Whiklo 
  4. Bethany Seeger 
  5. Andrew Woods  
  6. Ben Pennell 
  7. Ben Cail  (star)
  8. David Wilcox
  9. Peter Eichman 
  10. Daniel Lamb
  11. Mohamed Mohideen Abdul Rasheed
  12. Dan Field

Part 2: 

  1. Danny Bernstein
  2. Ben Pennell
  3. Ben Cail
  4. Bethany Seeger
  5. Peter Eichman

Agenda

  1. Announcements
  2. OCFL Community Call Update
  3. Landing the Sprint
    1. Set sprint closing meeting time 
    2. Issues in progress 
    3. Issues in review (PRs)
    4. Status of Search / Containment Index Design
    5. Handling RDF in Fedora 6
    6. Decisions and Open Questions
      1. Establishing clear description of F6's RDF (on disk, from non-Fedora OCFL, what changes, etc)
        1. Trim `ldp:contains` and other SMTs
        2. Normalize URLs to internal URIs
        3. Normalize serialization
  4. Draft functional requirements for repositories based on NDSA Levels of Preservation 2.0 (update)
  5. <Your question/topic here>


Tickets

  1. In Review

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

  1.  Announcements
    1. OCFL call - discussed a couple issues, planning to add some language to OCFL spec or implementation notes. Stanford has a new validator (Ruby gem).
    2. Desire to make sure Fedora 6 runs properly in the cloud. Can test S3 on OpenStack. Need details on what exactly people want to do in the cloud.
      1. ocfl-java client - starting to add support  for S3 (incomplete). More complicated, may have more requirements (eg. DB).
  2. Landing the Sprint
    1. sprint closing meeting - 1pm EST (Friday)
    2. issues in progress/review
      1. get to the point of running Fedora 6 - put something in, get it back out
      2. should make some good progress on PRs today. Things should be pretty clear. Get PRs merged even with some cleanup to do afterward.
      3. 3129 - implement get headers. Put together a proposal for fcrepo sidecar, then work on ticket.
      4. 3119 - try to get that in, base 3129 on 3119.
      5. migration-utils - things are progressing, single-stream.
      6. transaction piece -should be wrapped up this afternoon
    3. search/containment index design
      1. realigned with proposed interface, writing code to retrieve data from DB - WIP PR. Discuss later today.
    4. handling RDF in Fedora 6
      1. shared doc about handling server-managed triples, and OCFL objects from outside Fedora.
        1. 4 approaches: ignore SMT, how much to interpret RDF/directories on OCFL objects. How Fedora would behave in different cases.
        2. leaning toward ignoring SMTs, but still discussing.
        3. working on follow-up document.
        4. discuss more in Part 2.
        5. is it possible to push json-ld in, and get it exactly back out? Agreement to trim SMTs.
        6. info:fedora URI from Fedora 3 - could make it configurable to support multiple use-cases. Optionally translate URI prefix.
        7. roll out simplest things first, then add more features.
        8. should RDF files be containers? what should migration-utils do? Discuss in doc.
    5. design/open questions
      1. object deletions - root of Archive Group - add a tombstone, then delete ocfl object when tombstone is deleted?
        1. F4/5 - when object is deleted, you get a tombstone, and all the info is all lost
        2. what would other backends support? It's not part of the API. Could be specific to OCFL backend to allow bringing back an object that was deleted.
        3. could provide access to version history of tombstones, or not.
        4. Are people OK with the memory of a deleted object still being there?
        5. Could fit somewhat with Fedora 3 'D' state.

Actions


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.