Hydramata Project

Hydramata Project Update

Mon, 08 Sep 2014 00:00:00 +0000

The Works component of Hydramata is progressing with the goal of having a presentable walkthrough at Hydra Connect 2. It’s feature scope and development status is publicly viewable.

CurateND development priorities are dictated by a “living” document that you are welcome to peruse. This document links to JIRA tasks with further information. The JIRA instance is not open to the public as of this morning (2014-09-08). If you are interested in more detail Dan would be happy to provide it.

Dan will be available on Skype at this time (2:00–3:00 PM EST) every week if anyone would like to discuss project status.

Hydramata Sprint 2 Update

Mon, 21 Jul 2014 00:00:00 +0000

Capacity was decreased in sprint two due to vacation and training for several members of the team.

CurateND

Rajesh is continuing to work on replacing our legacy ETD system with CurateND.

Hydramata

Jeremy is continuing to work on Hydramata Works. The primary repo has been moved to the ndlib github organization. The repository will be moved to the hydramata github organization once its initial development is complete.

Jeremy has written a lot about what Hydramata is trying to accomplish:

Dan is drafting a document that articulates the differences in design philosophy between Hydramata and Hydra Head. He is also revising the Hydramata “vision” document to address the feedback from the last PO/PD meeting.

Roadmap Update

There is no change in which components are in progress since our last update.

Issue Status

No SWARM issues have been prepared for the next sprint. The team at Notre Dame will continue ongoing development.

Hydramata Sprint 1 Update

Tue, 24 Jun 2014 00:00:00 +0000

CurateND

There have been some changes to CurateND since it is in beta. CurateND is deployed from the master branch in the CurateND github repository. As bugs or changes have surfaced the team at Notre Dame will commit them to Curate as long as they makes sense as engine-level functionality. There are some stopgap features, such filtering the Work types that are available to users, that have been kept at the application-level when they serve ND-specific integration needs.

Rajesh has been working on two projects that will be batch ingesting Works into CurateND. He is migrating finding aid management for our Department of Rare Books and Special Collections and ETDs from our legacy ETD system into CurateND. The ETD migration will use the ETD Work type defined in Curate.

Curate does not support batch ingest. To address this Rajesh is transforming the data from the the legacy system to Don’s Raw Object Format. ROF can be used to batch-create Fedora objects. (NOTE: The Fedora objects will be created without their Solr document counterparts. Don and Banu are exploring different facets to this batch indexing problem.)

Rajesh is making good progress in both projects. Each case requires a corresponding Work type and presentation strategy. Although this is possible in Curate there is significant overhead. Hydramata will hopefully address this.

Curate

Notre Dame has forked Curate in order to have a stable foundation for the CurateND beta launch. The updates made to Curate are being committed to the “curate-nd-beta” branch. We want the Notre Dame fork of Curate to stay in sync with the upstream Curate repository. During the next sprint, which starts the week of 2014-07-07, the changes made since May 17th will be reconciled between the Notre Dame fork and Curate proper.

Hydramata

Jeremy has been working on the first of the Hydramata components: Hydramata::Work. The README articulates high-level and low-level tasks in its development and their respective status. At this point the groundwork has been laid for other developers to work in consort with Jeremy.

The Digital Library Technology Unit (DLT) at Notre Dame will be working with a front-end developer from another unit in the Notre Dame library during the course of CurateND development. He will start by defining the HTML generated by the in-memory objects marshaled in the core of Hydramata::Work. This task handoff will serve as the pattern for future work delegation between our teams. As that process improves it will serve as a basis for how SWARM tasks will be articulated. There will not be any SWARM tasks for at least the next two sprints. There will be 2–4 weeks advanced notice given for any developer commitments from other partner institutions.

Roadmap Update

The components in blue are in progress.

Issue Status

After much deliberation the DLT team at Notre Dame has decided to track Hydramata development tasks in the ND library JIRA. Keeping issues in our local JIRA will increase our capacity by improving our ability to collaborate with other units at ND. You can view the issues on our current sprint. There is filter to restrict the sprint view to only Hydramata tasks.

SWARM tasks will be mirrored on the DuraSpace JIRA. Other tasks can be mirrored there if there is a fortuitous alignment of need and desire. Chris reached out to DuraSpace to see if they would allow linking our two JIRA instances but they declined. If there is interest DLT would be happy to explore JIRA linking or other methods of issue syndication with other institutions.

Hydramata Project Update

Fri, 13 Jun 2014 00:00:00 +0000

Project Changes and Next Steps

There have been a lot discussions within the Hydramata project recently about how best to optimize our process, team makeup, and technology. These discussions have resulted in a refined Product Vision, Updated Process, Architectural Changes, Roadmap of Implementation, and restructured development team(s). To achieve the first phase of our refined vision and architectural changes, we will be shrinking the implementation team for re-architecting Hydramata over the summer to a small team primarily at Notre Dame. We will then bring in developers from other project partners as necessary and spawn additional development teams once we emerge from the core refactor. More specifics on next steps and other project changes are below.

Communication

Inspired by how Stanford engaged with the community for Spotlight, we will emulate their communication model to keep the community up to date with status updates and recorded demos.

Next Steps

Community Discussion of Design with Hydra committers
- During a Hydra committers call within the next few weeks we will review the current architectural design to get feedback on possible changes, any possible ripple effects for Hydra (especially work that could feed into changes related to Fedora 4)
While community discussions are happening, for the chance of a deliverable by October, 2014 at Hydra Connect 2
- A small team at Notre Dame will form to begin immediately to work against the roadmap laid out here: https://jira.duraspace.org/browse/HYDRASIR-542
- Goals for Hydra Connect 2 from the Roadmap document include:
  - Hydramata::Work will be complete
  - Hydramata::Workflow will be mostly implemented
  - Enough of Hydramata::Work and Hydramata::Workflow will be spliced into Curate to achieve a “demoable” state
- Notre Dame will implement the 3 Amigos/Story Triage process that was approved by the 5 partners
- Smaller team will include at various times Dan Brubaker Horst (PO), Jeremy Friesen (Tech Lead), Chris DeLuca (Scrum master and QA), Banu Lakshminarayan (Dev), Rajesh Balekai (Dev), and UI dev (from separate ND web dev team)
- SWARM: during core IR development we are leaving it open to expand team for SWARM activities based on availability of resources and progress of community discussions
- Cincinnati and Indiana are hopeful to contribute to swarming given resource availability and progress of community discussions
- Revisit team composition, parallel teams, etc. on conclusion of core IR development
- Smaller Project Team (at Notre Dame) will model Stanford Spotlight communication process
- Demos for the community (continue regular invitations of project partners to each sprint demo. Maybe record them for screencasts?)
  - Email Summaries of progress (also similar to Fedora 4)
  - Stories and tasks tracked in JIRA
Continue bi-weekly calls PD/PO to make sure we have a scheduled time to follow up on progress (next call July 14, 2014)

Hydramata Project

Hydramata Project Update

Hydramata Sprint 2 Update

CurateND

Hydramata

Roadmap Update

Issue Status

Hydramata Sprint 1 Update

CurateND

Curate

Hydramata

Roadmap Update

Issue Status

Hydramata Project Update

Project Changes and Next Steps

Communication

Next Steps

Governing Documents