Fedora 4 is moving toward linked data, but I don't know much more than that. I don't work with Fedora. In theory you could create a collection about the "Doe House in Ann Arbor, Michigan" and specify that any number of cultural heritage objects are part of that parent collection. I believe that most of LAM applications (both commercial and non-commercial) are behind this curve, though.

On Fri, Jan 16, 2015 at 3:00 PM, Michele R Combs <[log in to unmask]> wrote:

Hi Ethan –

Can you give me an example of an application that supports this?  Both commercial and home-grown would be of interest to us.

Thanks --




From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Ethan Gruber
Sent: Friday, January 16, 2015 2:41 PM
To: [log in to unmask]
Subject: Re: Related objects in digital repository?


Newer repository applications are becoming increasingly linked data aware, so you could use a variety of dcterms properties to record these sorts of relations.



On Fri, Jan 16, 2015 at 2:33 PM, Michele R Combs <[log in to unmask]> wrote:

Hello Collective Wisdom!

A question for those of you who are digitizing stuff and putting it online.  Do you somehow record the fact that two digitized objects are related to each other, and if so how do you do so?

For example: 30 videotaped interviews and 3 reels of news footage that were filmed as raw material for the production of a documentary; correspondence, bills, site surveys, photographs and blueprints relating to the building of a specific public building; etc.

It's easy in a finding aid, of course, since finding aids were designed to support this sort of hierarchical description.  Not so easy in a digital repository which is usually pretty flat.  So I'm curious what others are doing.

The simplest solution is to put the information in the narrative description, for example "Letter from John Doe to Jane Smith about changes to plans for the Doe House in Ann Arbor, Michigan," and then end users can do a search on the phrase "Doe House") to find all items that mention it in the description.

I'm wondering if anyone is doing anything more complex, robust, technically cool, etc.

Many thanks --

Michele Combs
Lead Archivist
Special Collections Research Center
Syracuse University Libraries
[log in to unmask]