Versions Compared

Old Version 1

changes.mady.by.user Unknown User (acoburn)

Saved on

compared with

New Version Current

changes.mady.by.user Danny Bernstein

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees 

...

Agenda

  1. New Committer, Bethany Seeger!
  2. Fedora 4.7.1 release status
  3. Status of fcrepo-connector-file
  4. Import/Export sprint update
  5. New public Fedora calendar (iCal)Defining/Documenting the Fedora API with http://swagger.io/
  6. Linked Data Notifications
  7. fcrepo-camel/fcrepo-camel-toolbox updates
  8. Performance and Scale call on Monday
  9. ...

  10. Status of "in-flight" tickets

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13202
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

...

  1. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  2. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  3. Tickets created this week:

    Expand
    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

  1. New Committer, Bethany Seeger!
    • Official announcement to the mailing list forthcoming. 
  2. Fedora   Feodra 4.7.1 release status
    • Bethany Seeger kindly volunteered to do the release, and will have a RC later today RC was sent out last Friday, there is a lot of testing outstanding as usual; windows in particular is in demand.  January 5th is the tentative date for release.
    • Release Testing - 4.7.1
  3. Status of fcrepo-connector-file
    • Ben Cail discovered it was being tested during the RC process
    • We've mostly forgotten about this and the main users (Esmé Cowles and Michael Durbin) no longer use it.
    • We've removed it from the release candidate testing
    Unknown User (acoburn) pointed out fcrepo-vocabulary that represents various RDF vocabularies in Java.  It will be an alternative to our current flawed string-concatenation method
    • .
    • Unknown User (acoburn) wishes to use it soon, but it will have to have a maven release, and to do so, he's suggesting we change the group name from org.fcrepo to org.fcrepo.api (and has issued a PR)
    • A. Soroka has a mild preference for "org.fcrepo" because people more commonly put API stuff there.
    • Unknown User (acoburn) agrees, but would like to avoid reusing/re-purposing existing artifact names and allow for separate version numbers for API stuff
    • Andrew Woods suggested an alternative of instead of changing group names now, just find new artifact names for other stuff later.
      • The approach going forward will be to change implementation-specific group ids.
      • The PR will be closed (not merged) and a release will be made
  4. As A. Soroka moved the spec forward, some questions have come up...
    • How to trigger running fixity checks?
      • Not related to "transmission fixity checks", but instead the "on-demand" fixity checks.
      • Nick Ruest and Benjamin Armintor developed a lovely model, but the question of the exact request is unclear.
        • The model involves creating a new resource (not just a transient part of the response) as the result of the fixity request that contains the current fixity evaluation.
      • The pros and cons of the two proposed methods hinged on whether typically non-mutating HTTP requests resulted in repository mutations and the confusing nature of the meaning and result of empty-body POSTs.
      • Esmé Cowles indicated that choices a and b are not mutually exclusive and we could do an empty-body POST with a want-digest header that specified the algorithm.
      • For clarification...
        • Every binary gets a versioned fixity resource automatically (against which the on-demand fixities can be triggered)
      • There were no objections or suggestions, and a general consensus that either approach was imperfect but acceptable.
      • ...until... Aaron Birkland questioned the need for fixity results to be persisted and wondered if it could be made optional somewhat like the audit pattern
        • Andrew Woods brought up that an advantage to persisting fixity results is that a message gets emitted and that some people have consistently wanted to get notifications (JMS) of those checks.
        • A. Soroka reminded us that we have a principle that we only emit messages when the repository changes, and that if we don't create resources, periodic (scheduled fixity checks) won't make it out of the repository
        • Aaron Birkland played the devil's advocate and walked us through a way one could achieve the expected results without adding this stuff to the spec.  (there was technical difficulties that diminished the ability to hear his arguments)  ... he later continued and asked what is the downside on placing the burden on the user to create a resource to log the fixity and build message receivers to respond to those messages.
          • A. Soroka indicated that some repository implementations may have periodic (repository instigated) fixity checks.
          • A. Soroka also conceded that one clearly could put this outside of the repository and punted to Nick Ruest who deferred to Benjamin Armintor's (absent from call) judgment
          • Andrew Woods asked interested users on the line how they might envision it
            • Jim Coble described their current approach in which the hydra application layer does all the fixity check work and records it outside of the repository (in the Rails active-record database).
            • Doron Shalvi has a use for synchronous request to get a fixity result and has the goal of having routine automated fixity checks and have those values stored somewhere.  The stuff has to be stored somewhere, and it would be convenient to store it in the repository.
        • Danny Bernstein pointed out that the point of fixity was to discover when something was corrupted and asked if messages were emitted when a failure was detected.
          • A. Soroka replied that intentionally there's just an event that indicates the new fixity result and that external tooling would be responsible for determining whether that event identifies a corruption.  He pointed out that in some case (like large videos) an intraframe fixity failure might require a more nuanced response than a simple "FAILED" "SUCCEEDED" binary.
  5. Nick Ruest thinks things are going "Very great"
    1. Summarized here... 2016-12 Import - Export Sprint 03 Meetings
    2. Is working with tool that validates exports as being identical to the repository content (Bethany Seeger's work)
    3. hopes to have real good progress on bag-it work by the end of next week.
  6. Andrew Woods glossed over this due to time, saying that "there is a calendar, it will be updated"
  7. Andrew Woods said this is interesting, we'll give it a look.
    • will move the repository to labs.
  9. Import/Export sprint update
    • Bagit import/export exists
    • Sprint is on pace
    • The LoC bagit library may pose some issues due to an out of date 5.0.0-beta release on Maven Central.  We want to use a later version as well as some issues with the library. https://github.com/LibraryOfCongress/bagit-java/issues/72
      1. May end up rolling our own bagit library.
  10. New public Fedora calendar (iCal)
    • Arising from the Fedora camp in NY, a public google calendar was created to be a centralised place for all Fedora meetings for your subscription pleasure.
  11. Linked Data Notifications
    • Unknown User (acoburn) spoke to this W3C spec that is currently in review, and had a conversation with the main writer (Sarven Capadisli) about this spec and Fedora. Fedora fits into the LDN spec as an implementation and may help the specification pass through the W3C review process.
  12. fcrepo-camel/fcrepo-camel-toolbox updates
    • New release forthcoming from Unknown User (acoburn) most likely next week.  These will be (potentially) minor breaking changes and will be a minor release.  For anyone that has been using the toolbox in the past it will require Camel >2.18.0 and there will be a few changes in the installation and configuration process.  Everything is an improvement for flexibility.
    • The major change is with fcrepo-camel, in the past it would act upon the JMS headers, but it is being refactored to match the Fedora Specification more closely and decouple JMS to allow other notifications like RabbitMQ.
    • This release is focused on modularity to allow greater flexibility.
    • Jared Whiklo asked about auth credentials in sub modules
      • Unknown User (acoburn) All auth credentials have been centralised barring ldpath which doesn't actually use fcrepo-camel
  13. Performance and Scale call on Monday
    • Note to the list and agenda will be forthcoming from Nick Ruest
  14. Status of "in-flight" tickets
    • Kevin Ford raises a potential re-occurence of FCREPO-2323
      • It has the appearance that URIs are being stored with localhost as the domain of the URI rather than the host server's domain.  Most triples have the defined apache proxy name, whereas some have the localhost.
        • String Literal or URI in RDF?
          • URI
        • What happens if you always go through the proxy?
          • All is well.
        • Unknown User (acoburn): if you are running a server on localhost, and connect to it, and use the server's FQDN fedora will see it as an external resource.  Should always use the FQDN.
        • Jared Whiklo experienced this in Islandora CLAW work, need to always set the host header to the canonical name, to avoid splitting the repository into seperate entities.
      • This is potentially by design based on Unknown User (acoburn)'s current understanding of the issue, as you can run afoul of local resources versus external resources.  Everything needs to go through a single entry point, in his implementation NGINX proxies fedora and handles rewriting the Host header so that it is always the FQDN, rather than an IP address.
      • Kevin Ford will open a related ticket to continue this discussion
  15. Next call January 5, 2017Andrew Woods reported that there was a camp and would have encouraged folks int he meetingKate reported on the meeting and her interest in a dev-ops interest group
    Andrew Woods will be offline until January