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

Compare with Current View Page History

« Previous Version 4 Current »

Time/Place

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

Attendee

  1.  Ben Pennell (star)
  2. Jared Whiklo  
  3. Aaron Birkland 
  4. Peter Eichman
  5. ...

Agenda

  1. Closing the loop on fcrepo-camel-toolbox and fcrepo4-vagrant for 5.x
    1. https://github.com/fcrepo4-exts/fcrepo4-vagrant/pull/91
  2. PRS: 
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  https://github.com/fcrepo4/fcrepo4/pull/1465
  3. Import Export "mini-sprint" Progress report
    1. Clarify expectations on how proxied files will be exported and imported (metadata exported, files moved by admin?)
  4. <your discussion point here>
  5. In Review

    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.

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

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

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

Notes

  1. fcrepo-camel-toolbox
    1. PR available for review, mainly need to verify the output in places like Fuseki.
  2. PRs
    1. FCREPO-1889 - Still needs a look, Peter previously had a script for this
  3. Import export - Just danny working on it at the moment
    1. Need to capture the locations from header - This would include ACLs, Mementos, external binaries
      1. Jared will create ticket for capturing design decisions about how to capture headers, and what headers to capture
    2. For proxied/redirect binaries, do not wish to capture the content of the binary, just the reference
      1. There is already an -x flag which lets you download the external binaries into the export (this may get strange in terms import and capturing headers)
    3. Seems like early summer may be a more likely time frame for a sprint
  4. Does fedora 4 still require pair trees for performance reasons?
    1. https://issues.jboss.org/browse/MODE-2109?_sscc=t
    2. https://docs.jboss.org/author/display/MODE40/Large+numbers+of+child+nodes#Largenumbersofchildnodes-Unorderedlargecollections
      1. Types of containers in mode shape
      2. These were never put into the default fedora CND
    3. It would be helpful to have Bess look at Fedora 6, get a sense of her use case for ark identifiers in fedora urls, flat hierarchies
      1. Add or update a use case for Fedora 6.

Actions

  • Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
  • Peter Eichman :  will complete review of  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  when Jared Whiklo  is finished with the above.
  • Peter Eichman : to review  Unable to locate Jira server for this macro. It may be due to Application Link configuration.



  • No labels