cmharlow

Keybase proof

I hereby claim:

• I am cmharlow on github.
• I am charlow (https://keybase.io/charlow) on keybase.
• I have a public key whose fingerprint is 0B2E 3909 623B 467D 430E 1C6F 2159 B821 4AF8 7C4C

To claim this, I am signing this object:

cmharlow

{
  "executionRoleArn": null,
  "containerDefinitions": [
    {
      "dnsSearchDomains": null,
      "logConfiguration": null,
      "entryPoint": [
        "./api"
      ],
      "portMappings": [

cmharlow

swagger: '2.0'
info:
  title: Draft SDR-PC API 
  description: >
    Writing up a test API specification for SDR-PC.
  version: 1.0.0
  contact:
    name: Christina Harlow
consumes:
  - application/json

cmharlow

909867566964785152
909852030889451520
909865301537259520
909861670272552960
909865250463219712
909863033366749184
909863343028162562
909865275528376320
909852490337865733
909860041754161152

cmharlow

- Current resource_type => edm:hasType <URI for value> (label: CV label for URI) ; dcterms:type <URI for type from DCMI>, <URI for type from LC> - Article => edm:hasType <http://vocab.getty.edu/aat/300048715> (label: articles) ; dcterms:hasType Text
- Audio => n/a ; dcterms:type (DCMI Types: Sound, LC Resource Types: Audio)
- Book => edm:hasType <http://vocab.getty.edu/aat/300028051> (label: books) ; dcterms:hastype <http://purl.org/dc/dcmitype/Text>, <http://id.loc.gov/vocabulary/resourceTypes/txt>
- Capstone Project => edm:hasType <http://id.loc.gov/authorities/genreForms/gf2014026039> (label: Academic theses) ; dcterms:hastype <http://purl.org/dc/dcmitype/Text>, <http://id.loc.gov/vocabulary/resourceTypes/txt>
- Conference Proceeding => edm:hasType <http://id.loc.gov/authorities/genreForms/gf2014026068> (label: Conference papers and proceedings) ; dcterms:hastype <http://purl.org/dc/dcmitype/Text>, <http://id.loc.gov/vocabulary/resourceTypes/txt>
- Dataset => n/a ; dcterms:type <http://id.loc.gov/vocabular

cmharlow

{"count": 462, "next": null, "includes-extra": false, "files": [{"filetype": "warc", "checksums": {"sha1": "4b0a36a69ba3d46a5d152d9c7fc78b94c5672c6d", "md5": "067d6680f273e4aa9dfd174529b5bafa"}, "crawl-start": "2015-12-24T09:47:06Z", "account": 925, "collection": 5425, "filename": "ARCHIVEIT-5425-CRAWL_SELECTED_SEEDS-JOB188828-20151227094353149-00022.warc.gz", "crawl": 188828, "size": 1000034362, "locations": ["https://partner.archive-it.org/webdatafile/ARCHIVEIT-5425-CRAWL_SELECTED_SEEDS-JOB188828-20151227094353149-00022.warc.gz"]}, {"filetype": "warc", "checksums": {"sha1": "95e2275091148c9f880abd8f5e02fb06f3a85c67", "md5": "92ff6581fa765364046e45ad20df49fe"}, "crawl-start": "2015-12-24T09:47:06Z", "account": 925, "collection": 5425, "filename": "ARCHIVEIT-5425-CRAWL_SELECTED_SEEDS-JOB188828-20151227040930645-00021.warc.gz", "crawl": 188828, "size": 1000004206, "locations": ["https://partner.archive-it.org/webdatafile/ARCHIVEIT-5425-CRAWL_SELECTED_SEEDS-JOB188828-20151227040930645-00021.warc.gz"]}, {"filety

cmharlow

Hyrax Metadata Specifications & Documentation

Table of Contents

• About (this page)
• Core Hyrax Metadata Application Profile

Goal(s) & Scope of metadata-docs/

This metadata-docs/ directory contains metadata technical documentation and specifications that don't fit in the existing codebase documentation methods, but require management, a review process, and versioning beyond what is captured in the GitHub wiki. In particular, when a Hyrax version is released, the metadata-docs/ travel with the codebase and indicate the current metadata specifications followed in that release. This documentation doesn't indicate recommendations for individual implementations of Hyrax (your metadata documentation will no doubt vary), but aims to clarify what metadata specifications exist in the core Hyrax codebase.

cmharlow

1. Would Article resources be of class hw:Range, using pcdm:hasMember to point to a list of component parts?
2. Okay for that rdf:List of component parts to be the Page resources (pcdm:Object), NOT the Filesets (per the hydraworks definition for Range)?
3. What does this gain us that not using option 1 (just more proxies, iana for ordering) doesn't?
4. Would Article (Range) resources still be (pcdm) members of the Issue resource? Pages make sense in this regard.
5. What does Range gain us? Fewer proxies? Closer alignment with IIIF?
6. Can our (CUL)'s current Hydra setup for working with F4 (Curation Concerns, not Hyrax, not Sufia) work with these Range resources - aka, how do they appear in the editor? In the interface? In search and discovery?

cmharlow

822830885665902593
822864513376669703
822913402452508672
822837247305093120
822734580591579137
822862970275368961
822841230920925184
822852304432807936
822926509392310272
822917075719045120

cmharlow

#!/usr/bin/env python
import pymarc
import sys

input = sys.argv[1]
output = input + '.xml'

reader = pymarc.MARCReader(open(input, 'rb'), to_unicode=True)
with open(output, 'w') as writer:
    writer.write("<collection xmlns='http://www.loc.gov/MARC21/slim'>")