Time/Place

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

  • Time: 11:00am Eastern Daylight Time US (UTC-4)
  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free:  http://www.readytalk.com/intl 
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
    • Once on the call, enter participant code 2257295
  • IRC:

Attendees 

Agenda

  1. Recent PCDM updates

    1. https://github.com/duraspace/pcdm/issues/23
    2. https://github.com/duraspace/pcdm/pull/2
      1. https://github.com/duraspace/pcdm/pull/27
    3. https://github.com/duraspace/pcdm/issues/21
  2. Landing in-flight issues
    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. HydraConnect3 and associated Hydra/Islandora Best Practices – desired outcomes?
  4. ...

  5. Please squash a bug!

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

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

  • PCDM Update (mostly just to highlight work, rather than to discuss here)
    • There is some discussion going on at https://github.com/duraspace/pcdm/pull/27 (Changing file-format-types to be RDFS instead of OWL) on whether things should be named individuals or classes. Several folks have weighed in and if you have opinions on the topic please add them to the discussion.
    • Work underway to have a basic stylesheet so the ontology can be easily viewed on the Web
    • External files are an important Fedora use case and work is happening in PCDM to represent them
    • Many of the folks working on PCDM will be meeting at Hydra Connect and will discuss whether an addition forum/list for discussion would be useful or whether the discussion on GitHub are the best place
  • Walkthrough of some of the "in-flight" tickets
    • FCREPO-1294 details OutOfMemoryErrors that are happening with long running ingests. The ticket has some useful tools mentioned in the comments which could be used with memory logs to better diagnose the problem.  Osman and Esme both indicated in a couple of weeks that they'd have some time to take a look at what's going on.  If not a resolution, a documented set of suggestions for dealing with the issue (e.g., different JVM args) would be a good outcome.
    • FCREPO-1519 describes a need to serialize binaries and RDF to disk. Esme might be able to take a look at this too in the context of his upcoming ingests, but others are also welcome to dig in. The desired goal is a Camel component that does this.
    • FCREPO-1407 is a particular request to have the fixity information published, but discussion covered that and the larger issue of redesigning fixity and where fixity information should live. Now, it can live internally in an audit area or can be persisted to a triplestore through the Camel layer. There was some discussion about whether it's better to handle fixity internally through the REST APIs or through the Camel layer. Andew suggested closing this more specific ticket (to publish fixity information) and to take a step back and open another one for the design issues which need further discussion/exploration.
    • FCREPO-1581 is about an upgrade Modeshape to 4.4. Clustering is the blocker with the upgrade. There are currently two clustering issues, one which is a local internal issue (which can be resolved relatively easily) and the other is that an upgrade to Modeshape 4.4 would break clustering for us for other reasons (changes in Modeshape/Infinispan configuration files). The Modeshape upgrade is important because it addresses the scalability issues around hierarchies and the question of whether anyone was currently using clustering or not was raised – and, whether it would be okay to put out a new release with the newer Modeshape, but which would not support clustering.  Work then in another brach to resolve the Modeshape/clustering issues would happen and could be included in a future release.  Involved with this is the need to do backwards/forwards compatibility testing so that the Fedora disk from an older version of Fedora will work with a newer release. So far changes have been compatible and some testing needs to happen to make sure that is still the case.  This will be done in the new branch.
    • FCREPO-1561 if for large literals that can't be deleted because they're being stored in a different location (for binaries). Bethany is currently investigating the issue and making progress.
  • Action item for anyone who is an assignee on the "in-flight" tickets. Please go through and update it or stop work on it if work isn't currently being done.  It would be better to have a smaller number of in-flight issues.
  • Andew and some others will be out next week at HydraConnect and Nick volunteered to run the meeting. There were a reasonable number of people who won't be attending HydraConnect so they'll have the meeting at its regular time.

 

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.