EAD dates not importing

45 views
Skip to first unread message

Adele T

unread,
Mar 26, 2012, 11:21:14 AM3/26/12
to ICA-AtoM Users
Hi everyone,

I am playing around with an EAD import and cannot get my dates to
work.

Can someone spot what is wrong?

My two different attempts at the EAD code so far:

<unitdate datechar="creation" encodinganalog="3.1.3"> 22/11/50 </
unitdate>
*No error message but it just doesn't appear.

<unitdate type="creation" encodinganalog="3.1.3"> 05/11/51 </unitdate>
*Error message:
libxml error 502 on line 28 in input file: Value "creation" for
attribute type of unitdate is not among the enumerated set

I took the ' normal="1951/1951" ' out of the tag because in data-entry
it usually magically appears and it is just easier for me to ignore
it...if that is possible.... Also, when I had it in the tag, the
import still did not work.

I will appreciate greatly any ideas! Thanks,

Adele
Reference Archivist
UNESCO Archives

Tim Hutchinson

unread,
Mar 26, 2012, 11:48:53 AM3/26/12
to ica-ato...@googlegroups.com
Hi Adele,

The first thing to check would be whether your <unitdate> is nested
below <did>. That's where the default import routine is looking for it.

Your second example isn't valid EAD - type needs to be "bulk" or
"inclusive" (note that this is currently ignored by the import routine).
If you leave out datechar it will default to creation. I haven't worked
much with the normal attribute, but that should also be retained (though
I recall an earlier discussion about the precise syntax required for
import).

Tim


--
Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Dr.
Saskatoon, SK S7N 0G2
(306) 966-6028
e-mail: tim.hut...@usask.ca

Adele T

unread,
Mar 27, 2012, 4:14:49 AM3/27/12
to ICA-AtoM Users
Thanks very much, Tim! I gave it another go with the tag below and I
couldn't get it to work. But do you think it looks normal now and
could hypothetically work?

<unitdate normal="1952" encodinganalog="3.1.3"> 17/01/1952 </
unitdate>

It is nested in the <did>, but I have a bunch of tags all in one long
line, like the below. Blank fields from the source database just give
empty tags (like scope and content), but with the index terms this is
causing funny values, so I need to go back to delete them. Is this
too messy to work, do you think? It is only the date that is not
working out.

<c level="file"> <did><physloc>C003.5</physloc><container
type="Coffre"> 11 </container> <unittitle encodinganalog="3.1.2"> Note
of the United Nations informing that the Government of PAKISTAN has
deposited on the 17 January 1952 the Instrument of ratification of
the agreement on the importation of Educational, Scientific and
Cultural Materials (with protocol). </unittitle> <unitid
encodinganalog="3.1.1"> A/1/9 </unitid> <unitdate normal="1952"
encodinganalog="3.1.3"> 17/01/1952 </unitdate> </did> <scopecontent
encodinganalog="3.3.1"> <p> </p> </scopecontent>
<controlaccess><geogname> Pakistan </geogname> </controlaccess>
<controlaccess> <corpname> </corpname> </controlaccess></c>

Again, thanks for the advice!
Adele

Tim Hutchinson

unread,
Mar 27, 2012, 11:01:33 AM3/27/12
to ica-ato...@googlegroups.com
Hi Adele,

You might try eliminating the linebreak that puts the opening tag for
<unitdate...> on two lines. I tested with your snippet and initially
wasn't able to import anything, until I removed the linebreaks. But
after that I was able to re-introduce linebreaks, and it still worked,
so I'm wondering if your export routine is introducing a non-standard
character or something, on which the parser is choking.

Tim

JBushey, ICA-AtoM Product Manager

unread,
Jul 25, 2012, 2:05:34 PM7/25/12
to ica-ato...@googlegroups.com
I have created Issue 2384 http://code.google.com/p/qubit-toolkit/issues/detail?id=2384. Please feel free to edit the issue to better capture the problems being encountered with importing EAD and dates.

Regards,
Jessica Bushey
Reply all
Reply to author
Forward
0 new messages