I've been following this conversation as a non-coder. I'm really interested in getting a better understanding of linked data and how to use existing metadata for proof of concept linked data outputs. So, I totally think Eric's approaches are valuable and would be something I would use. I also understand there are many ways to do something better and more "in the flow." So, just encouraging you all to keep posting thoughts in both directions!
Elizabeth "Lisa" McAulay
Librarian for Digital Collection Development
UCLA Digital Library Program
email: emcaulay [at] library.ucla.edu
From: Code for Libraries [[log in to unmask]] on behalf of Eric Lease Morgan [[log in to unmask]]
Sent: Thursday, December 05, 2013 8:57 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] transforming marc to rdf
On Dec 5, 2013, at 11:33 AM, Mark A. Matienzo <[log in to unmask]> wrote:
>> At the very least, these applications (ArchivesSpace,
>> Archivists’ Toolkit, etc.) can regularly and systematically export their
>> data as EAD, and the EAD can be made available as linked data.
> Wouldn't it make more sense, especially with a system like ArchivesSpace,
> which provides a backend HTTP API and a public UI, to publish linked data
> directly instead of adding yet another stopgap?
Publishing via a content management system would make more sense, if:
1. the archivist uses the specific content management system
2. the content management system supported the functionality
“There is more than one way to skin a cat.” There are advantages and disadvantages to every software solution.