Time/Place

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

Attendees 

Agenda

  1. Topics for tech list

    1. Kevin Ford's issue from list

    2. ...
  2. Fedora API Specification meetings

  3. Potential 4.7.3 release

    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.

    1. Need upgrade utility:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  4. ...
  5. Status of "in-flight" tickets

    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.

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.  No good resolution to Kevin's issues yet.  
    1.  Andrew put together an export metadata  from modeshape tool.  Kevin has not yet had time to run awoods' tool.
    2. Kevin will run as soon as he can.
  2. Fedora API Specification: 
    1. New editorial team met yesterday
      1. discussion focused on external content
      2. Esme put forward a proposal in response:  

        https://github.com/fcrepo/fcrepo-specification/wiki/External-Content

        1. Fedora should proxy the content

        2. Client should not have to worry about the details of how the content is managed.
        3. If you have questions or comments,  you can add comments notes to the document above
        4. Open weekly API Spec calls Wednesday 2:30-3:30 Eastern
        5. Fedora 4 only supports redirect, not proxy
          1. One redirect use case:  sometimes you want to download the content from a difference source (for performance reasons) but manage all metadata in fedora
          2. Proxy makes fedora responsible for access control
  3. 4.7.3 Release:  
    1. wait for Andrew for timing and migration utility planning
    2.  Calling it out:  we are moving forward with  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  to support import export sprint.


  • No labels