Time/Place

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

Attendees 

Agenda

  1. Review of OR2016 outcomes and summer priorities
    1. API
    2. Import/Export
    3. 4.6.0 release
  2. Fedora 4.6.0 release plan?
    1. Support influx of Sufia7 users' use of JDBC over LevelDB ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
    2. Support ModeShape 5.1 – although we should not wait on ModeShape

    3. Support WebAC alignment with Hydra community

    4. Common logging practice in fcrepo-http exception mappers?

  3. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
  4. Commons RDF in fcrepo-kernel-api
  5. Support for fcrepo4-oaiprovider
  6. Review of fcrepo4-labs and fcrepo4-exts for shifting
  7. ...
  8. Status of "in-flight" tickets
  9. 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.

Ticket Summaries

  1. 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.

  2. 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.

  3. 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.

Minutes

  1. OR 2016 review
    1. Esme: There was general interest in the API spec, but not necessarily specific changes or engagement
    2. David: Leadership group voiced support for import/export implementation and for API effort
      1. Well-attended workshop on the first day, including more Europeans than we see in North American events, good experiences with Fedora 4, but barriers to migrating custom frontends from Fedora 3
      2. Good session "Repository Rodeo" including Fedora, Hydra, Islandora, Eprints, DSpace and Invenio — great way to position Fedora relative to other platforms
    3. Andrew: Lots of interest in OAI provider (see agenda item #5), which has not been maintained for recent release.  Could be a good opportunity for people who want OAI provider to contribute.
      1. Interest in leadership group to support import/export of Bags.
        1. Esme: Princeton is interested in using Bags for import/export and could help implement
        2. Ben: Using Bags locally, using for transport, from Archivematica
      2. Import/export functionality rapidly becoming a blocker for Modeshape 5
  2. Fedora 4.6.0 release planning
    1. Esme: I have encountered a bug in the modeshape5 branch, where loading an object with many attached files, trying to debug and reproduce without having to setup a Hydra ingest stack.  Looks related to the 299th item, not the specific file, or the binaries.  Will try to narrow down to whether it happens in master or with MySQL, etc.
    2. Andrew: Keeping modeshape5 branch current with master, will force-push new commits to that branch.
      1. Not inclined to wait for Modeshape 5.1 release, to get updated WebACL aligned with Hydra community, support incoming Sufia 7 users
      2. We should make sure the WebACL updates are tested and really work
        1. Ben: Will talk to Andrew later today to try to get someone working on Sufia to test a current Sonatype build
    3. Ben: Working with Duke on their sporadic migration errors, would like to standardize some of the debug logging to make debugging easier.
      1. Andrew: There's a ticket and PR that may be related:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  — this might potentially address their issue.

      2. Esme: If adding the versionable mixin is causing problems, can we just add the versionable mixin by default in the CND?

      3. Ben: The draft API spec says that resources should have a header declaring that they are versionable: http://fedora.info/spec/2016/05/20/resource-versioning#common-http-response-headers and that requests can set headers to indicate that, and the implementation could add the versionable mixin or otherwise enable versioning.

  3. Support for fcrepo4-oaiprovider
    1. David: We talked about this before, but wanted to bring up that this came up at OR and seems like we need some work here to keep this module working.
  4. Review of fcrepo4-labs and fcrepo4-exts for shifting
    1. Andrew: There is some discussion of reviewing -labs and -exts and everything in -exts is appropriate, but there may be a few in -labs that might be ready to promote or archive.  Will send an email to the list asking about this.
  • No labels