LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


EAD@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  October 2004

EAD October 2004

Subject:

Re: Where does encoding fit in the processing timeline? Who does it?

From:

Mike Ferrando <[log in to unmask]>

Reply-To:

Encoded Archival Description List <[log in to unmask]>

Date:

Wed, 20 Oct 2004 13:14:15 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (170 lines)

Michele R.,
Hi.

1. We have a finding aid manual for data collection methods, display,
and standards of bibliographic description. There is also an index of
example pages from finding aids.

2. Data collection is usually done in word processors (WordPerfect).
However, there are some collections that are done in Access
databases. Special characters (multi-byte) are chosen from the
character-map utility. Arial Unicode MS is used as the font for mdb
files. Times New Roman is used for WordPerfect. If MS Word is used,
Arial is the font.

3. Each finding aid goes through a review process of experienced
archivists in order to comply to the standards (see 1).

4. Coding can be done only an experienced finding aid creator and
collection processor can interpret such a document. I code the
finding aids. I have over 10 years experience with archival
processing and I am one of the co-editors of the finding aid manual.
I also process the word processor documents into their final form.
The hard copy is now a PDF (created using XSL-FO from the EAD 2002
XML document). I write the stylesheets and have created the workflow
for the finding aids.

5. I have developed macros that tag the finding aid container list in
an XML tag set I developed based on MARC 21 standards. This method is
quick and efficient. The finished container list then is converted
using Unicode tools into UTF-8 (0020 to 007E). Other steps are taken
for cross references, etc. The MARC record is brought into the
workflow and constitutes the front matter, excepting any finding aid
information (scopecontent | bioghist, etc.) A stylesheet then renders
the XML into the current EAD tag set. Once in EAD 2002 XML there is
one stylesheet for HTML and one for XSL-FO (PDF). These stylesheets
are based on the Library of Congress best practices. I have created
them to work with 99% of the valid EAD 2002 XML finding aids.

I have created a demo of this process (though a bit dated):
  Maximize browser window
  Paste in URL
  Temporary window opens for 20 seconds
  Click on "Next Slide" bottom right.
  Refresh to begin again
http://lcweb2.loc.gov/music/eadmusic/eadmusictest/eval_04_x/matrix-1.html

6. Critique of data collection:

a) My preference is that multi-format material be described in a word
processor. The word processor I would choose (because of budget,
availability and experience of data collectors) is Notepad. If you
have an updated Windows operating system (2000, XP, etc.), then this
will work. You should choose font as Arial Unicode MS, and use the
character-map utility for muti-byte characters. Everything else is
the same. Sure you don't get the fancy formatting options, but data
collection does not really need them.

b) Databases. I think databases can do "almost" anything. Your
database is usually only as good as your support staff has designed
it to be. I think that most offices have only workstation database
software. These programs are really toys. They are very unstable and
can be easily corrupted. (Are they on general use PC's?) Working over
a network can really screw up your database unless you are configured
correctly. Such configuration takes time and support and mostly
money. Thus, we have only workstation databases.

c) Learning curve. Learning bibliographic description according to
AACR2 and SAA is difficult enough, but then learning to use the
database as well? Strictly speaking, data collection is easily
relegated to word processors. Easily entered, edited, printed, viewed
and the format (tabs, bold, italic, etc.) is more universally
understood. Databases usually result in a mess, unless you have staff
to QC all the button pushing and other user errors (not to mention
the nasty auto grammar issues: auto caps; replace ellipses with
special characters, etc. You fixed those... Whoops they updated the
software...). Databases are a lot of time to set up and configure
(who has admin rights?), and more time to correct and clean up.
Further, their are many parts of a finding aid that simply cannot be
carried into any reasonable practice in a database (scopecontent,
etc.). (Finding aids are usually hierarchical, databases flat.)

d) Coding. I would completely separate coding from data collection.
The coder should be coding datatypes using a standard (MARC 21). The
coder should clearly understand the elements of the EAD tag set as
they relate to these datatypes. The coder should attempt to establish
consistent methods in approaching difficult if not impossible
conversion issues (double titles when uniform titles are given; use
of attributes PERSNAME/@NORMAL, etc.). Mostly, the coder needs to be
aware of the stylesheet that will transform the EAD into some display
markup in order to get the most out of the coding methods developed.
This is not a weekend experience for anyone, even experience
archivists. A best practices is really needed. The Library of
Congress best practices document is awesome.

e) Archiving documents. This document workflow requires a backup
system (separate originals from working copies). My goal was to
create a single master document for each finding aid. I have achieved
that in my workflow now that I can produce PDFs from the EAD. These
documents will need revision, correction, and sometimes additions.
How will this be done, and by whom? Who will hold the archived
electronic documents, and where will they be stored? I regularly burn
CD-ROMs of these finding aids (XML). My experience is that most
institutions don't have a backup system at all. If there is one, it
is hardly comprehensible to anyone outside the immediate backup
person. Finally, if that "person" is "not here today", there is no
paper trail, nor any second person that can produce any archive
copies for uploading (in case of virus, etc.).

These are reflections on my experience as a coder for the past 3-4
years.

Again, I profited greatly from Daniel Pitti's class.

Sincerely,
Mike Ferrando
Library Technician
Music Division
Library of Congress
Washington, DC
202-707-4454


--- MicheleR <[log in to unmask]> wrote:
> Hello -- another question, this one regarding process of encoding
> finding
> aids.  I'm interested in (a) who does the encoding and (b) at what
> point in
> the process the encoding is done.  For example, I can see at least
> three
> options right off the bat:
>
> a) finding aids are originally written in EAD using authoring
> software (e.g.
> XMeTaL)
> b) finding aids are written in regular form (MSWord, etc) and then
> encoded
> at the end by the processor
> c) finding aids are written in regular form (MSWord, etc) and then
> encoded
> at the end by a dedicated encoder (either in-house or out-sourced)
>
> How do most people do it?  What pitfalls have you encountered with
> the way
> you chose?
>
> Any and all information is appreciated.  We're investigating
> starting this
> process and would like to benefit from combined wisdom as much as
> possible!
>
> Thanks
>
> Michele Rothenberger
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.778 / Virus Database: 525 - Release Date: 10/20/2004
>




__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
December 1995

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager