Versions Compared

Old Version 1

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user David Wilcox

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Agenda

  1. Announcements
    1. 2020 Q1 Sprint Doodle: https://doodle.com/poll/es7nwdppt94rv2pz
  2. Fedora Leaders Call Update
  3. State of the code review: open tickets
  4. Fedora 6 Demo
    1. What
    2. When
  5. Open Questions
  6. Fedora API Versioning
    1. https://docs.google.com/document/d/1eNtkWx1sANLuf07poayLFd-KovbPGJqMYKpQu6kXTVk/edit?usp=sharing
  7. <><your topic>

Tickets

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


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

2020 Fedora 6 Sprints

  • Danny sent out a Doodle poll
  • Only a few people have filled it out so far
  • Anyone interested in participating should fill out the poll

Fedora Leaders call update

  • Andrew reported on sprint outcomes and sang the praises of the tech team
  • Announced sprint demo to be recorded next week
  • Full notes are available

State of the code review

  • Bethany finished 3060
    • Implements replace properties on an RDF source
    • Once we can test the full system we may discover some bugs
  • Ben working on 3129
    • Getting resource headers for resources in the persistence layer
    • Hoping to finish this up today
    • RDF sources need sidecar files in order to be treated as RDF rather than as binaries
    • File structures are described in this document
    • migration-utils does not currently create sidecar .fcrepo directory. Should it?
  • 3119 closed, includes many tests against OCFL persistent storage session
  • Danny rebased 3126, which deals with versioning
  • 3105 parked for now, Jared will close in favour of opening a more updated ticket
  • 3103 should be put back in progress based on feedback
  • 3082 probably lower priority
  • Can we close open pull requests that are older than a year? They are likely to be irrelevant given the Fedora 6 changes
    • Everyone should review over the next two weeks and comment on any that we should keep

Sprint demo

  • What and when? Migration demo will take place next Monday
  • What do we want to accomplish from the demo? It probably doesn't need to be bug free.
    • Demonstrate read/write containers and binaries
  • Need to get feedback on Ben's proposal to finalize how content looks on disk in OCFL before organizing a demo
  • Demo for the tech team first, then put something together for the community


Actions

...