Versions Compared

Key

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

...

  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. Leaders call was good.  Update on F6 development work, with a focus on developing a better communications plan around the work.
  2. State of the Sprint
    1. Intensified design work which has resulted in discrete, actionable tickets
  3. Design questions
    1. Should Fedora be able to store checksums for fixity checks?  General thoughts are "Yes, this is preservation software after all"
      1. Further still, should checksums for external binaries be stored so as to avoid charges when using services such as S3 and Glacier?
    2. Simple Search
      1. Sync vs Async
        1. Consensus seems to be around a synchronous search, as that provides value.  Asynchronous methods are generally untrusted.  There is also some desire to replicate Fedora 3's functionality w/r/t simple search
        2. Transactions make things tricky (as always), and there's questions around when to update the search index and whether or not you can search within a transaction.
    3. Other open questions
      1. 1:1 mapping between Fedora info URIs and LDP paths
        1. Continue with current model and solicit feedback on it.
      2. What to do with the converter framework?
        1. One of the more complicated parts of the code base
        2. Will not be neccessary to convet object types, but this ID/String to that ID/String would be neccessary.
  4. Fedora 3 to 6 migration work has started using Peter Winckles 's OCFL library.  You can check out the progress here: Fall 2019 Migration-Utils Planning

Actions

  •  Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
  •  Andrew Woods will look into java 11 transition
  •  David Wilcox will review the NDSA matrix and pull out the concrete technical requirements that could be considered during the Fedora 6 development.

...