Time/Place

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

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

    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.

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. New Committer, Bethany Seeger!
    • Official announcement to the mailing list forthcoming. 
  2. Fedora 4.7.1 release status
    • Bethany Seeger 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
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. Performance and Scale call on Monday
    • Note to the list and agenda will be forthcoming from Nick Ruest
  9. 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
  10. Next call January 5, 2017

 

 

  • No labels