Embracing Technology

On the first day of my Introduction to Archives class, my professor made certain to emphasize the fact that, while the archival field certainly involves a great deal of work with “old stuff,” itÂ’s also very much concerned with and immersed in the realm of “new stuff,” that is, technology. ArchivistsÂ’ relationship with technology is twofold:  they are tasked with preserving and making available information stored on machine-dependent materials (e.g., floppy disks, VHS tapes, the Internet) and with using technology to make their collections as accessible as possible (putting them online, making them searchable, etc.). I have not had the opportunity to do a great deal of work with digital preservation yet, but IÂ’m excited to take Archiving and Preserving Digital Media later on in the GSLIS program. I have, however, had the opportunity to learn about the other side of technology in archives in a course IÂ’m taking this semester called Archival Access and Use.

One of the main purposes of this course is to teach students the archival description standards and practices currently prevalent in the field. When archivists create finding aids, which describe their collections, it’s important for them to make them as accessible to users as possible. Many repositories go about doing this in different ways.  In general, however, most strive to at least display finding aids online using HTML and, if they are associated with libraries, make them discoverable in the library catalogs by encoding them using MARC (MAchine-Readable Cataloging). Many archives also encode their finding aids using the XML standard known as EAD (Encoded Archival Description).  Doing this turns finding aids into powerfully searchable tools and makes them easier to index in repository databases, thus facilitating access in multiple ways. EAD is what we are currently focusing on in class, and I’m finding it’s something I really enjoy learning.

I was never especially “techie” prior to coming to Simmons GSLIS. I suppose I’m a member of “Generation Y” because I have grown up with computers; I remember playing Snake on my dad’s MS-DOS-based PC as a toddler. Even so, I never took more than a functional interest in computers–they were there and I generally knew how to get them to do what I needed them to do. I honestly was a bit intimidated at the idea of learning behind-the-scenes skills like HTML and being introduced to anything that involved the word “encoding.” I knew, though, that it’s important for archivists to have at least a basic understanding of these skills and concepts, so I gave myself a pep talk and walked into the first class of EAD with an open mind.

It turns out that, largely thanks to my tendency to pay an extreme amount of attention to detail, IÂ’m the kind of person who likes EAD! The instruction IÂ’ve received has definitely been effective. Three weeks ago, seeing this picture would have inspired me to hide under the covers, but now itÂ’s something I understand because I wrote it myself. It doesnÂ’t intimidate me anymore!

I’m grateful for the technology training I’m receiving in the Simmons GSLIS program and I know it’s definitely going to come in handy down the road–I’ll have a nice set of skills to list on my resume and be more adept as a professional. Also, it turns out, the nitty gritty computer stuff can be pretty fun!

2 Comments

  1. Katie Katie
    Posted March 20, 2012 at 1:29 pm | Permalink

    Ok, first, I’m extremely jealous. We just learned XML in my Intro to Technology class and I was more than overwhelmed. I couldn’t get the code right in class and I swear it was exactly like his example. I’m taking Access and Use online this summer with Kathy Wisser and I’m definitely going to have to brush up on it. Any suggestions?

  2. Posted March 20, 2012 at 11:22 pm | Permalink

    It might be of comfort to know that I haven’t taken Intro to Technology yet–you don’t have to have a perfect understanding of XML to be able to work with EAD! I don’t know what you’re doing in class, of course, but if you were stuck creating a schema/DTD then don’t worry because you don’t have to do that with EAD. The schema is maintained by the LOC it’s a lot of plugging and chugging rather than creating code.

    As far as tips go…hm. The software should alert you to issues; if the error/invalidity messages don’t make sense, try Googling them to see what others have said about them. Look for open tags that need closing. And, I think most importantly, try not to get overwhelmed! Try to view your red invalidations as puzzles you get to solve–there is a way for it to all come together!

    Also, sometimes all one needs is another pair of eyes, so get another XML-aware friend to check out your code if you get stuck. Feel free to E-mail anything my way and I can do my best to crack it. :)