Time/Place

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

Attendees 

Agenda

  1. Updates on 4.7.4 release.

  2. Fedora alignment to API sprints
    1. Delta document - Additions would be helpful
    2. Spec editorial seeks feedback on impact of changes
  3. Versioning the root node? 
  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
4.7.4 Release

It's done.  Jared Whiklo had issues with bad html within Javadocs but worked around it.  Now on to 4.8 or maybe 5.0?  Jared will send a note to fedora-tech to let people know it's available.

There's a PR on the 4.7 maintenance branch to bring the RC back in which will need to be handled with care given the nature of the commits to the RC branch.  It might be best to wait for Andrew Woods to get back before moving forward on this.

Fedora Alignment Sprints

People are encouraged to go through the differences and add to the Delta document.  There are also several issues in the fcrepo-specification queue that will bring changes to Web AC and are worth checking out.

Versioning the root node

Consensus was on removing the feature because it is not well advertised through the API and not something we want users to embrace.

Pair-Tree Nodes

Unable to locate Jira server for this macro. It may be due to Application Link configuration. Proposal to create a Prefer header value to allow clients to selectively traverse the tree, which would result in more smaller requests during traversal.  The root node was observed to take over 15 minutes to load, and was timing out during re-indexing.

Andrew Woods threw some POC code up on Github: https://github.com/fcrepo4/fcrepo4/compare/4.7.4-RC...awoods:aw-no-pairtree


  • No labels