You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Time/Place

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

Attendee

Agenda


  1. Feedback on /fcr:fixity  endpoint
    1. Fedora API Specification github issue
  2. Getting to 5.0 
    1. Review of work that happened this week: 
      1. External content (proxy, copy, and redirect)  - PR merged, there are a few issues relating to it that are low hanging fruit. 
        1. 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. 5.x Documentation Effort
      1. 5.x Documentation Updates matrix
    3. Another sprint? 
      1. Timeframe/Duration/Availability
    4. Ecosystem tools dependent on the release:
      1. import export tool
      2. camel tool kit  
      3. fcrepo4-vagrant
      4. java client 
      5. api-x 
  3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    1. Are we comfortable with messages emitted?

  4. Progress Report on Fcrepo-Cloud-Migrator Tool
    1. variants in .ttl between the python export and ruby-rdf

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

  • Look at fcr:fixity in JIRA - creating a ticket and look at options
  • See if possible option for fixity checking could be an API-X service
  • Talk to API Spec group about returning fixity check result as an additional header, returned on 'want-digest'.  
  • Peter Eichman - See how tightly bound our current implementation is to modeshape, in regards to the fixity endpoint.  Can look at at the end of next week.
  • Message to list-serve to see who might be using fcrepo-java-client outside of fcrepo-camel


  • No labels