an open source toolkit for geospatial metadata work.
Goal to try and make Spotlight feed in a IIIF manifest to ingest an item.
Did some demos to go from CD-Rom with data on it to a map interface using CartoDB.
- Currently a searchworks branch.
- Can add a tag to a file.
- A staff member can add things like "about science."
- Tags are stored separately from metadata in Triannon (Fedora) store. If metadata changes, tags are still there.
- You can search by tags.
- Interoperate tags between institutions
- December 13, got a grant
- Assembling an ontology and linked data sources to provide relationships, metadata, and broad context for scholarly information resources.
- Create a standard to exchange resources.
- Go beyond bibliographic data.
- Connect with faculty profiling information
- Why Linked Data
- Flexible/extensible
- Growing ecosystem
- Wide range of tools/ontologies
- Linked data cloud image.
- Convert from "Strings to Things"
- Go to URIs
- Get concrete - stories as the basis of use cases.
- 42 raw use cases.
- 12 refined use cases in 6 clusters.
- Bib + Curation Data
- Bib + person data
- Leverage external data including authorities
- Leveraging the deeper graph
- Leverage usage data
- Three-site services e.g Cross-site search
- LD4L data sources
- How do we connect to LOD web?
- Map bibliographic data to BIBFRAME
- Use ontologies commonly found in linked data.
- Connect research profile info
- Create persistent, stable local URI IDs
- Link local IDs to global IDs (ORCID/VIAF/ISNI)
- VIVO
- Open search semantic-web based researcher and research discovery tool.
- Standard ontology that interconnects researchers, communities, and campuses using Linked Open Data
- Broad community
- Connects scientists and scholars through their research and scholarship
- Semantic web application
- Provides RDF/HTML
- Self-describing data
- Provides search & query augmented by relationships
- Underlying Vitro code supports generic edit/display of ontology and instances
- Service that provides granular, open access to a large and growing aggregation of Harvard library metadata through APIs - a metadata hub.
- http//library.harvard.edu/librarycloud
- https://github.com/harvard-library
- Harvard's Instance
- Contains records from ILS (12.7M bib records), VIA (4M images), OASIS (2M finding aid components)
- Amazon Queues does Ingest -> Normalize (MADS) -> Enhance -> Distribute APIs (OAI/PM/Download/etc)
- Authentication/Authorization
- Collection API.
- Technology Stack
- Uses Amazon - spins up 10 instances for ingest.
- Scripted - deploying LibraryCloud builds up all these servers.
- Implementing ORE
- ORE can do sets or ordered lists.
- In simplest form it's just aggregating a bunch of resources
- ORE:Aggregation
- Gem provides business logic end of how all the predicates go together.
- Indiana had a lot of users using the bookmarks functionality.
- There's a dropdown to add to folder when selecting items
- Can look at folders
- Creating Folders
- Name them
- Can set visibility to "anyone" or "only me"
- If you share it publically you can pass it on to others.
- Only the owner has edit rights
- You can rearrange the order of the items in the folder
- Cite/Email/Export to Endnote/Refworks
- If you have bookmarks already there's a rake task to move everything over.
- Students go through and mark chapters as doing transcription work.
- Taking all the annotations, putting them into solr, and providing facet search through Blacklight.
- Blacklight can view the IIIF image, IIIF metadata, and display them in a basic blacklight view which can link back to Mirador.