Print

Print


Hello,

referring to <origination> on item level we are doing as follows:

- <c04 level="file">
- <did>
  <unitid type="Bestellnummer">NS 1 7003</unitid>
  <unittitle>Dossier Dr. Lindemann, Leiter des Heimes Wernigerode/Harz</unittitle>
  <unitdate normal="1937-10-11/1939-03-10" era="ce" calendar="gregorian">1937-10-11 - 1939-03-10</unitdate>
- <origination label="final">
  Lebensborn e.V.
  <corpname role="orgunit">Hauptabteilung Gesundheitswesen</corpname>
  </origination>
  <repository>Internationaler Suchdienst (ITS), Bad Arolsen, Germany</repository>
  <abstract type="Enthält u.a.">Enthält u.a.: Aufnahme in die SS; Rücktritt als Heimleiter</abstract>
- <physdesc>
  <extent>18 Bl.</extent>
  </physdesc>
- <unitid type="former reference number">
  Lebensborn 29, Bl. 1-16
  <title linktype="simple">neue Ordnernummer</title>
  </unitid>
- <unitid type="former reference number">
  L II 1, Bl. 1-16
  <title linktype="simple">alte Ordnernummer</title>
  </unitid>
- <unitid type="former reference number">
  Hist. 39, Bl. 1-16
  <title linktype="simple">Nr. der ehem. Hist. Abt.</title>
  </unitid>
  </did>
  </c04>

Karsten Kühnel, M.A.
Abteilungsleiter Katalogisierung
Head of Division Archival Cataloguing

International Tracing Service
Große Allee 5-9
D-34454 Bad Arolsen

Phone: +49 (0)5691 629-0
Direct: +49 (0)5691 629-146
Fax:   +49 (0)5691 629-501
E-Mail: [log in to unmask]

http://www.its-arolsen.org


-----Ursprüngliche Nachricht-----
Date:    Wed, 7 Dec 2011 11:29:39 -0500
From:    Jaime Margalotti <[log in to unmask]>
Subject: Use of <origination> in <did>

Hi Folks,

We've been trying to set up our EAD finding aids so that they can easily
map to Dublin Core for the sake of our digital projects.  We've been
able to map collection-level elements with no problem, but I'm having
some issues at the item level.  The materials in this case are digitized
oral history interviews.

For mapping purposes, I need to somehow indicate the creator at the item
level.  It appears that it is valid to include <origination
label="Creator"> in the <did>.  Is anybody actually doing this?  If not,
do you have another solution?  Any suggestions would be appreciated.
Currently the creator of each item is just part of the <unittitle> and
not tagged in any additional way.

Thank you,
Jaime

--

Jaime L. Margalotti
Senior Assistant Librarian
Special Collections Department University of Delaware Library
Newark, DE  19717-5267
302-831-0554
[log in to unmask]

------------------------------

Date:    Wed, 7 Dec 2011 17:18:57 +0000
From:    Michele R Combs <[log in to unmask]>
Subject: Re: Use of <origination> in <did>

<origination> is the semantically correct element to use, so I'd go with th=
at.

You don't mention what the end use of this data is, but in cases where the =
entire collection (or a huge proportion of it) has the same creator, it mig=
ht be possible for the c0#s in the inventory section to inherit the creator=
 from up above in archdesc/did/origination.  Then you would only have to in=
clude an <origination> for c0#s where the creator differs, and have it over=
ride the inherited one.  Depends on how the EAD is being processed / used /=
 massaged / whatever.  Inheritance is a powerful component of XML; it would=
 be nice to take advantage of it and would save a lot of coding effort.

Michele

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Be=
half Of Jaime Margalotti
Sent: Wednesday, December 07, 2011 11:30 AM
To: [log in to unmask]
Subject: Use of <origination> in <did>

Hi Folks,

We've been trying to set up our EAD finding aids so that they can easily ma=
p to Dublin Core for the sake of our digital projects.  We've been able to =
map collection-level elements with no problem, but I'm having some issues a=
t the item level.  The materials in this case are digitized oral history in=
terviews.=20

For mapping purposes, I need to somehow indicate the creator at the item le=
vel.  It appears that it is valid to include <origination label=3D"Creator"=
> in the <did>.  Is anybody actually doing this?  If not, do you have anoth=
er solution?  Any suggestions would be appreciated. =20
Currently the creator of each item is just part of the <unittitle> and not =
tagged in any additional way.

Thank you,
Jaime

--=20

Jaime L. Margalotti
Senior Assistant Librarian
Special Collections Department University of Delaware Library Newark, DE  1=
9717-5267
302-831-0554
[log in to unmask]

------------------------------

Date:    Wed, 7 Dec 2011 21:01:40 +0100
From:    Wim van Dongen <[log in to unmask]>
Subject: Re: Use of <origination> in <did>

--_000_908FFDBAE111214C83B962AB8888BCAF90BF1A37DAOWWNLMBX001oc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Jaime,



I agree with Michele: it's best to inherit the archdesc/did/origination inf=
ormation to the c-levels and use that information in Dublin Core records pe=
r digital object. In fact that's what we have implemented in the backend of=
 the Archives Portal Europe to be able to forward information on digital ar=
chival objects from EAD finding aids to the Europeana portal, which is usin=
g a Dublin Core based data model. I have recently showed this during a mapp=
ing conference in the Bundesarchiv in Berlin: www.archivgut-online.de<http:=
//www.archivgut-online.de>.



Best regards,



Wim van Dongen

Nationaal Archief - The Netherlands

technical coordinator APEnet project

www.apenet.eu<http://www.apenet.eu> - www.archivesportaleurope.eu<http://ww=
w.archivesportaleurope.eu>

________________________________________
Van: Encoded Archival Description List [[log in to unmask]] namens Michel=
e R Combs [[log in to unmask]]
Verzonden: woensdag 7 december 2011 18:18
Aan: [log in to unmask]
Onderwerp: Re: Use of <origination> in <did>

<origination> is the semantically correct element to use, so I'd go with th=
at.

You don't mention what the end use of this data is, but in cases where the =
entire collection (or a huge proportion of it) has the same creator, it mig=
ht be possible for the c0#s in the inventory section to inherit the creator=
 from up above in archdesc/did/origination.  Then you would only have to in=
clude an <origination> for c0#s where the creator differs, and have it over=
ride the inherited one.  Depends on how the EAD is being processed / used /=
 massaged / whatever.  Inheritance is a powerful component of XML; it would=
 be nice to take advantage of it and would save a lot of coding effort.

Michele

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Be=
half Of Jaime Margalotti
Sent: Wednesday, December 07, 2011 11:30 AM
To: [log in to unmask]
Subject: Use of <origination> in <did>

Hi Folks,

We've been trying to set up our EAD finding aids so that they can easily ma=
p to Dublin Core for the sake of our digital projects.  We've been able to =
map collection-level elements with no problem, but I'm having some issues a=
t the item level.  The materials in this case are digitized oral history in=
terviews.

For mapping purposes, I need to somehow indicate the creator at the item le=
vel.  It appears that it is valid to include <origination label=3D"Creator"=
> in the <did>.  Is anybody actually doing this?  If not, do you have anoth=
er solution?  Any suggestions would be appreciated.
Currently the creator of each item is just part of the <unittitle> and not =
tagged in any additional way.

Thank you,
Jaime

--

Jaime L. Margalotti
Senior Assistant Librarian
Special Collections Department University of Delaware Library Newark, DE  1=
9717-5267
302-831-0554
[log in to unmask]

--_000_908FFDBAE111214C83B962AB8888BCAF90BF1A37DAOWWNLMBX001oc_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style title=3D"owaParaStyle"><!--P {
        MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<p>Dear Jaime,</p>
<p><font face=3D"times new roman"></font>&nbsp;</p>
<p><font face=3D"times new roman">I agree with Michele: it's best to inheri=
t the archdesc/did/origination information to the c-levels and use that inf=
ormation in&nbsp;Dublin Core records per digital object.
</font><font face=3D"times new roman">In fact that's what we have implement=
ed in the backend of the Archives Portal Europe to be able to forward infor=
mation on digital archival objects from EAD finding aids to&nbsp;the Europe=
ana portal, which is using a Dublin Core
 based data model. I have recently showed this during a&nbsp;mapping confer=
ence in the Bundesarchiv in Berlin:
<a href=3D"http://www.archivgut-online.de">www.archivgut-online.de</a>. </f=
ont></p>
<p><font face=3D"times new roman"></font>&nbsp;</p>
<p><font face=3D"times new roman">Best regards,</font></p>
<p><font face=3D"times new roman"></font>&nbsp;</p>
<p><font face=3D"times new roman">Wim van Dongen</font></p>
<p><font face=3D"times new roman">Nationaal Archief - The Netherlands</font=
></p>
<p><font face=3D"times new roman">technical coordinator APEnet project</fon=
t></p>
<p><font face=3D"times new roman"><a href=3D"http://www.apenet.eu">www.apen=
et.eu</a>&nbsp;-
</font><font face=3D"times new roman"><a href=3D"http://www.archivesportale=
urope.eu">www.archivesportaleurope.eu</a>
</font><br>
<br>
________________________________________<br>
Van: Encoded Archival Description List [[log in to unmask]] namens Michel=
e R Combs [[log in to unmask]]<br>
Verzonden: woensdag 7 december 2011 18:18<br>
Aan: [log in to unmask]<br>
Onderwerp: Re: Use of &lt;origination&gt; in &lt;did&gt;<br>
<br>
&lt;origination&gt; is the semantically correct element to use, so I'd go w=
ith that.<br>
<br>
You don't mention what the end use of this data is, but in cases where the =
entire collection (or a huge proportion of it) has the same creator, it mig=
ht be possible for the c0#s in the inventory section to inherit the creator=
 from up above in archdesc/did/origination.&nbsp;
 Then you would only have to include an &lt;origination&gt; for c0#s where =
the creator differs, and have it override the inherited one.&nbsp; Depends =
on how the EAD is being processed / used / massaged / whatever.&nbsp; Inher=
itance is a powerful component of XML; it would
 be nice to take advantage of it and would save a lot of coding effort.<br>
<br>
Michele<br>
<br>
-----Original Message-----<br>
From: Encoded Archival Description List [mailto:[log in to unmask]] On Be=
half Of Jaime Margalotti<br>
Sent: Wednesday, December 07, 2011 11:30 AM<br>
To: [log in to unmask]<br>
Subject: Use of &lt;origination&gt; in &lt;did&gt;<br>
<br>
Hi Folks,<br>
<br>
We've been trying to set up our EAD finding aids so that they can easily ma=
p to Dublin Core for the sake of our digital projects.&nbsp; We've been abl=
e to map collection-level elements with no problem, but I'm having some iss=
ues at the item level.&nbsp; The materials
 in this case are digitized oral history interviews.<br>
<br>
For mapping purposes, I need to somehow indicate the creator at the item le=
vel.&nbsp; It appears that it is valid to include &lt;origination label=3D&=
quot;Creator&quot;&gt; in the &lt;did&gt;.&nbsp; Is anybody actually doing =
this?&nbsp; If not, do you have another solution?&nbsp; Any suggestions wou=
ld
 be appreciated.<br>
Currently the creator of each item is just part of the &lt;unittitle&gt; an=
d not tagged in any additional way.<br>
<br>
Thank you,<br>
Jaime<br>
<br>
--<br>
<br>
Jaime L. Margalotti<br>
Senior Assistant Librarian<br>
Special Collections Department University of Delaware Library Newark, DE&nb=
sp; 19717-5267<br>
302-831-0554<br>
[log in to unmask]</p>
</body>
</html>

--_000_908FFDBAE111214C83B962AB8888BCAF90BF1A37DAOWWNLMBX001oc_--

------------------------------

End of EAD Digest - 6 Dec 2011 to 7 Dec 2011 (#2011-122)
********************************************************


This e-mail communication (and any attachment/s) are confidential and are
intended only for the individual(s) or entity named above and to others who
have been specifically authorized to receive it.

If you are not the intended recipient, please do not read, copy, use or
disclose the contents of this communication to other. Please notify the
sender that you have received this e-mail in error by calling the phone
number indicated or by e-mail, and delete the e-mail (including any
attachment/s) subsequently.

This information may be subject to a professional secrecy (e. g. of
auditor, tax or legal advisor), other privilege or otherwise be protected
by work product immunity or other legal rules. Thank you.