CURATEcamp 2010

• MPI 2 I/O API - the I/O section of the Message Passing Interface API
• Consistency part of said API

File formats:

• more time for intro to micro-services
• more room to describe a session topic than just a post-it
• shorter times slots, esp. for lightning talks that won't take an hour
• break between hour slots
• do report-outs from sessions
• work harder to solicit interesting stuff that people are doing (some people are shy)
• code code code -- bring code plus docs to next meeting

Strategic plan for content stewardship at Penn State. In order to
implement digital management, they want to find curation services that
would meet those needs.

There are few use cases on ingest, management, etc. that can be
applied to developing and automating things for a microservices
approach.

• MyExperiment - http://www.myexperiment.org/
  
• Islandora - http://islandora.ca/
  
• LEAD - https://portal.leadproject.org/gridsphere/gridsphere
  
• Kepler - https://kepler-project.org/

Is it peer-to-peer or master-slave relationship?

Mark Phillips: microservices approach at UNTexas. Assumptions: boundaries of an object

Arsenic and a Cron job to replicate files doesn't necessarily work
because of physical drive arrangements between two sets of servers.
Instead they use a manifest and walk it to move the files.

Stanford University Libraries Blacklight site

UVirginia: http://search.lib.virginia.edu/

Northwest Digital Archives Blacklight installation: http://nwda.projectblacklight.org

uses Solr for indexing.

Internet Access: