Versions Compared

Key

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

Questions and practicalities

practicalities

...

Troubleshooting production DB connection problem?

...

  • Environment var management?

    • envyable?

  • How to curate, manage, maintain a set of test files / data?

    • use rspec

  • Does Blacklight provide REST APIs?

    • You can get search results but maybe not facets?

  • What db are most people using? postgres? How to move from sqlite to postgres?

    • use what you know or is supported by your IT department

    • (sqlite is not for production)

  • What decisions do I need to make before I launch into production? what decisions can I change later on?

    • what id do you want to use?

    • object model in fedora - don't even worry about it for the first 50-100 thousand items

    • don't store anything exclusively in solr

...

  • is XML completely deprecated in fedora 4?

    • Doesn't sound like it. Get more info. Mark recommends examining your use cases – legacy XML from fedora 3? maybe model it that way for fed4. Ultimately he says it doesn't matter what format you store the data in, i.e. same from a user standpoint. (fair enough)

    • Reasons to use XML

      • You have very hierarchical data in nice, clean XML that someone is attached to

    • Reasons to use RDF

      • It's the current direction of the community

      • code is a little bit simpler

      • more specific / self-describing / natively self-authoritizing

      • You have data-sharing use cases

  • how / when is bagit used with fedora? hydra?

    • bagit is for storing collections of files / metadata in remote locations. we have no reason to worry about this at the moment.

  • MIRA: open source?

  • General Linked Data conversation

    • marmotta and fedora both implement LDP (linked data platform) which is a brand new w3c specification

    • Marmotta is currently being used in conjunction with fedora by people who want to cache external linked data sets for local use. (e.g., only the relevant portions of LCSH, and only on an as-needed basis)

    • Linked Data Fragments is super new and it's not clear yet how useful it will be

    • LDP: http://www.w3.org/TR/ldp/

    • Fedora3 used "data streams" Fedora4 uses the concept of "attachments" (see LDP). Fedora uses an RDF triplestore (fedora3 had to do a lot of serializing and deserializing and parsing). Fedora still has binary datastreams (used for attachments, non-RDF stuff).

    • You can theoretically use SPARQL directly into fedora's triplestore. but this would be a bad idea slash only for very expert people.

  • How does hydra/fedora handle preservation? E.g. checksums.

    • Fedora4 doesn't yet carry forward all the technical support for this that Fedora3 had. That's why there is current work around an audit service.

    • archivematica people believe that there are holes in hydra preservation. archivematica

    • Can you use fixity checks built in to your storage platform? If so, don't do it in fedora / hydra.

    • https://github.com/psu-stewardship/scholarsphere/wiki/Fixity-in-Sufia-with-Fedora-4 - confirm that this doc is still relevant and ask to talk to these people.

    • There is a Hydra preservation interest group (note for Michelle)

    • Other things to be aware of: provenance and history of edits - planned auditing service will take this on. Currently / formerly everything was recorded as a single user.

    • Consider thinking about fedora storage formats. What happens if you lose fedora?

  • What does it look like to upgrade?

    • Have sufficient test coverage

    • Make sure all tests are passing

    • Increase versions of dependencies in your Gemfile

    • Run tests and observe failures.

    • Start turning tests green

...

  • scholarsphere
  • dl.tufts.edu - tufts digital library - put a hydra head on top of existing fedora repo. awesome transcription / TEI w/ embedded timecode / audio player
  • levysheetmusic - changes / customizations to interface
  • hullhistorycentre.org.uk - hull city archives - example of EADs. (nice search box page!)
  • hydra.hull.ac.uk - has a backend with workflow stuff. would likely be happy to give a short demo. (also note interesting icons)
  • alexandria digital research
  • spotlight (stanford) - library.stanford.edu/projects/spotlight - for exhibit building. - note: blacklight gallery gem gives you different views of results lists.
  • another gem: date slider
  • digital.case.edu (built on worthwhile, rdf-driven) - open seadragon + iiif-compliant server for amazing image viewing. view metadata / different formats.
  • dl.tufts.edu - MIRA (management of institutional repository assets. more workflow-type, controlled deposit. 
  • http://demo.curationexperts.com/
  • WGBH - digitize on-demand. Metadata is published and there's a button.
  • HydraDAM (replaced Artesia at WGBH)
  • single EAD site (blacklight-only) http://bassiveratti.stanford.edu/en/catalog

 

Syllabus

  Image Modified

March 9th-13th, 2015

Yale University Library

New Haven, CT

Course Goals  

The goal of Hydra Camp is to introduce new developers to the skills and tools they will need to successfully build Hydra based digital repository solutions.  There’s a lot of ground to cover and you won’t walk out at the end of the week a complete expert, but we hope we’ll have provided you enough of a scaffolding to jump-start your own work and keep learning like the rest of us.  We hope that the topics covered at Hydra Camp provide enough breadcrumbs that you’ll have a good idea where to start looking once you get home and start digging into problems on your own!

Supplies

  • Laptop & Power Supply

  • Headphones/Earbuds

  • Water bottle/Travel Mug


Location

Prerequisites  

...

  • Local Development Environment Requirements

    • If you’re using a Mac, install/update XCode & homebrew.  

    • Install Git (on Mac, we recommend using homebrew to install git)

    • Install RVM + Ruby 2.1.5 using RVM `rvm install ruby-2.1.5`

(if you follow the installfest exactly, 2.0.0 also works fine)

    • Install Java 7 runtime (if you already have 6 installed, that also works)

    • Install Rails 4.1.9: `gem install rails 4.1.9`

    • Install a Text Editor of your choice.   KomodoEdit is a popular free option.  Many people use TextMate (not free). VIM is hardcore but some of us do it.

    • Create a (free) Github Account if you don't already have one: https://github.com/signup/free

    • Create Github SSH Keys and set them up for your development machine

  • NOTE: We’ll have help available in class if you run into any troubles getting your system set up.  We’ll have the VirtualBox image configured with Ubuntu and the necessary tools to complete class exercises or can help install all necessary software locally.


Syllabus

https://docs.google.com/document/d/10YeaUkYV-akfLQhqVd7Zffy_UxosdDUgzu6RxuIsxBA/edit#

Day 1: Monday, March 9th

  • MORNING - start 9:00am

  • DINNER  - on your own


Day 2: Tuesday, March 10th

See links to examples under Resources

  • LUNCH - on your own

    • [Optional] Start modelling your own metadata

    • [Optional] Create some additional content (books) to search

    • [Optional] http://vim-adventures.com 

  • DINNER  - group dinner @ TBA (?)


Day 3: Wednesday, March 11th

https://github.com/curationexperts/hydradam/wiki/Production-Installation%3A-Overview


Day 4: Thursday, March 12th


Day 5 [BONUS]: Friday, March 13th

  • Blacklight workshop







Image Modified

 


RESOURCES





  • Sample code for exercises

https://gist.github.com/afred/660e8f43026ad08a992d




 def show_my_stuff(solr_parameters, user_parameters)

...