...
Call for maintainers for any of the 6
WebAppPluswebapp-plus: awoods
Transform: whikloj, acoburn
...
This still leaves Audit, MessageConsumer, and WebAppPlus webapp-plus with 0 or 1 maintainers
Without owners, note that these modules are to be put on the fence, staying where they are
...
HydraConnect
Daniel Lamb was there...absent for this callInteroperability
Two sessions...one was a preconference event on the Monday night
Not much on what Islandora is doing wrong for Fedora 4
Hydra focused upon what they are improving (e. g. binding their Views)
Discussion landing on PCDM as least common denominator
Islandora over Fedora 4...Hydra over same Fedora 4...ideally, be able to have an admin view of Fedora resources
Lot of interest among the group in moving Hydra forward
Abstraction in Fedora 4...a standardized API is currently being established
PCDM conversation in particular is moving forward within the community
Addressing issues of value to the Hydra community
Esme is progressing with a branch is moving towards resolving 1742 E-Tags
E-Tags are generated solely based upon last modified date (managed by ModeShape)
Doesn't always work...issue with inbound references (i. e. cases for referencing between repository resources)
Updating B so that it references A...updates timestamp for resource A
Some parties find this behavior to be valid and appropriate...because the one potential representation has been changed for A
Others which develop applications that rely on E-Tags find that changing the timestamps often can trigger failures
Strong E-Tags should be Weak E-Tags
Reasoning: Strong E-Tags are byte-for-byte identical with regards to response
With content negotiation, responses aren't byte-for-byte identical, but the E-Tags are same
Further, for a higher-level application (e. g. Hydra) weak E-Tags have additional benefits
Migration Interest Group
Workshop at HydraConnect (all day on Monday, three parts)
Woods: Core features and hands-on exercises
Armintor: Session on migration using fedora-migrate; ActiveFedora 8 connecting to fcrepo 3; ActiveFedora 9 connecting to fcrepo 4 and migrating the content
Lamb: Integrating with external components via Apache Camel...just used fcrepo-camel (didnt use reindexer, solr, triplestoreupdater); How can you integrate with Fedora using Camel (using routes defined in XML)
Re-ran migration utility...using Camel routes for image resources, filtered for just JPEG images, executed ImageMagick, and re-ingesting the thumbnail as a child of the resource with the image
Session later in week: Hydra, migrating into fcrepo4 (A Woods, B Armintor on interest group)
Hydra community is in the position: no active development for fcrepo3 stack; how do I get on to Fedora 4 then?
Hydra is strictly focused upon fcrepo 4; Hence, IG was born (define practices, documentation around migration)
(Within Hydra context, a consistent way of migrating into fcrepo4)
Exercising the limits of the Fedora stack
People are being drawn to the fcrepo4 projectCurrent and potential scalability appeals to these new parties
Concrete descriptions of tests are desired
These render it easier for individuals coming into project...leading to the creation of infrastructure and the addressing of testing
Infinispan and the potential of the fcrepo4 stack (particularly focusing upon scalability targets)
Create isolated test scenarios
Interested Parties
- whikloj
- osmandin
- acoburn
- awagner
- jrgriffiniii
- ajs6f (Volunteering to Help)
Call to starting a Google Doc
Over the next couple of weeks, collectively come up with a test plan
Please include everyone in the community if this is initiated; otherwise, A. Woods will address after traveling
This should be an outline of a test plan...again, refer to the work of the Technical WG
Examples of Test Cases:
- Scaling for resources
- Scaling for a number of bytes
- scaling for a large repository collection
- iterating over reads
- performing an operation offline and pushing back updates
- at each resource, POSTing back an update
Include references for components at the Infinispan layer
Also discuss deployment into the cloud (particularly AWS)
...
Cleaning up Vagrant
N. Ruest has progressed much with the Islandora ecosystem
Vagrant Box with main components installed in the base box
Pulls down pertinent versions of Fedora components...installing all of the infrastructure for the Box
Question of Packer/Vagrant for Docker?
Deep-dive for next installation...sorting out the Packer discussion
Working with Yinlin's Docker image
Still need expertise for Packer
N. Ruest: Each institution requires its own Vagrant
ksclarke: has a number of features which he has to offer