Hi Michael,
It is the relationship that interests me, because it seems to me to be about the sort of relationships that Linked Data is out to capture. This Performance Database is not about 'material' in an archival sense; in fact, it's not about 'stuff' at all; it does not have a specific relationship to the archives. The links would simply an attempt to give researchers easy access to related information that is likely to be of interest to them, e.g: "You are interested in photographs from the play Happy Days…so you might be interested to find out more about this play - when and where it was performed, who starred in it, etc."
The funny thing with <odd> is that I've realised I kind of blank it out of my thinking. I think its because I have a sense that its 'everything else that doesn't fit into the defined categories', which is something I usually try to avoid! However, I can use the 'type' attribute to define the relationship more specifically. I'd definitely like to define the principle of linking to another information source to give additional information where it is not about material or any kind of archival context, and I should be able to do that using <odd> with attributes.
cheers,
Jane
On 12 Feb 2014, at 01:39, foxmjc <[log in to unmask]>
wrote:
> Jane,
>
> In my earlier response, I overlooked one other option, <odd>, Other Descriptive Data. The question is simple but the answer is problematic: what is the nature of the relationship of the information in these two systems?
>
> Michael Fox
>
>
> Sent via the Samsung Galaxy S™III, an AT&T 4G LTE smartphone
>
>
> -------- Original message --------
> From: Jane Stevenson
> Date:02/11/2014 8:31 AM (GMT-07:00)
> To: [log in to unmask]
> Subject: Re: Working with theatre archives and a performance database
>
> HI Michele,
>
> Yes, that might be best. It is not 'related materials' in the archival sense so much as 'additional information you might be interested in' because it is not about linking out to 'materials' as such. But I'm not sure there is something that semantically covers that kind of relationship specifically. In the end it is the 'association to the described materials' that I think is the key.
>
> cheers,
> Jane
>
>
>
>
>
> On 11 Feb 2014, at 14:57, Michele R Combs <[log in to unmask]>
> wrote:
>
> > <relatedmaterial> seems logical. Within that you could use extref (link to an external site).
> >
> > -----Original Message-----
> > From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Jane Stevenson
> > Sent: Tuesday, February 11, 2014 8:58 AM
> > To: [log in to unmask]
> > Subject: Working with theatre archives and a performance database
> >
> > Hi there,
> >
> > We are interested in linking from EAD descriptions of theatre archives (e.g. archives about 'Happy Days': http://archiveshub.ac.uk/data/gb71-thm/396/thm/396/4/1/15) to a performance database entry for 'Happy Days' that links theatre performances, writers and actors.
> >
> > We're considering the best way to do it. I wondered if anyone has any experience of doing anything similar? I can't really put the links into <controlaccess> because its about the archive not external sources, and <bioghist> is about the creator of the archive, which may not be appropriate. It doesn't belong in 'otherfindaid' because it is not another finding aid the archive but rather a means for researchers to go from an archival descriptions across to an environment that will give them a different context.
> >
> > I can see how it might work in a Linked Data context, but we'd like to consider a fairly low barrier option for the time being of simply adding URL's from our archival descriptions to an appropriate place in the performance database.
> >
> > with kind regards,
> > Jane.
> >
> >
> >
> >
> > Jane Stevenson
> > The Archives Hub
> > Mimas, The University of Manchester
> > Devonshire House, Oxford Road
> > Manchester M13 9QH
> >
> > email:[log in to unmask]
> > tel: 0161 275 6055
> > website: archiveshub.ac.uk
> > blog: archiveshub.ac.uk/blog
> > twitter: twitter.com/archiveshub
|
