4.3. De las Políticas Remunerativas
4.3.6. Información relevante de personal
http://digital.library.wisc.edu/1711.dl/wiarchives State(s) Included Wisconsin Summary of Mission
Archival Resources in Wisconsin: Descriptive Finding Aids presents archival finding aids describing collections held at 24 repositories throughout Wisconsin.
Number of institutions with collections represented in your aggregation 24 locations; 13 contributing repositories
List of Contributing Institutions
Center for the Study of Upper Midwestern Cultures (CSUMC), La Crosse Public Library, UW- Eau Claire McIntyre Library, UW-Green Bay Cofrin Library, UW-La Crosse Murphy Library, UW-Madison Archives and Records Management, UW-Madison Libraries – Mills Music Library, UW-Madison Libraries – Special Collections, UW-Milwaukee Libraries – American Geographical Society, UW-Milwaukee Libraries – Archives, UW-Parkside Library, Wisconsin Historical Society (WHS), Wisconsin Veterans Museum (WVM)
Number of Records
7,289
Record Type(s) EAD (2002)
Records Added in Last Year 143
Contributors Added in Last Year Yes; 1 plus 1 pending.
End Users
K-12 students, College/university undergraduate students, College/university graduate students, College/university faculty (primary focus: teaching/classroom), College/university faculty (primary focus: research/scholarship), Digital humanists, Professionals (non-academic researchers; administrators; legal researchers), Creative artists (visual, writers, musicians), Genealogists/family historians, Local historians, Collectors, Archaeologists, Journalists, Legislators and Museum Curators from other institutions
They have had no specific conversations at the aggregation level about end users. The
aggregation as a whole is higher education focused, but the majority of the finding aids are from the Wisconsin Historical Society.
Infrastructure
Main System for Storage, Indexing, and Delivery
DLXS (Digital Library eXtension Service) Open-source middleware which relies on a licensed proprietary indexer/search engine.
Other Elements of System
Contributors have sftp access to a development environment where they can submit EADs for automated validation and indexing. The DLXS middleware uses modules written in PERL, with XSLT stylesheets that are the primary vehicle for web display. Hosting is via the University's Library Technology Group's Systems component, on legacy Solaris servers. We anticipate migrating to the principal Linux server architecture within a year. Significant development was done to offer PDF versions of EADs via XSL-FO transformations, but never fully implemented. Persistent URLs are provided via CNRI Handles. EAD bibliographic records are exposed via UWDCC's OAI portal — https://oaidp.library.wisc.edu/oaicat/OAIHandler?
verb=ListRecords&metadataPrefix=dc_qual&set=wiarchives
They hope to update the infrastructure soon, but do not yet know what they will use instead. They are early in these discussions, but preliminary possibilities include SOLR indexes and possibly a combination of SOLR and eXistDB. They could maintain EADs in backend Fedora repository, with updates deriving from ArchivesSpace exports.
Do you host the content or harvest it?
Hosted: You host archival description records. End users view and interact with the records directly on your aggregation website.
Degree of Customization
Heavily (we've refined the system heavily to meet our needs)
How much do you customize for participating institutions?
Relationship to other systems or infrastructures at your organization or participating institutions
Archival collection management system (ArchivesSpace, Archivist’s Toolkit), Institutional Integrated Library System (ILS), Shared Integrated Library System (SILS), Repository Registry, OAI Repository (digital objects), ArchiveGrid.
● ArchivesSpace is not integrated, but something they are dealing with as institutions adopt it.
● Integrated Library System/Shared Integrated Library System: There are MARC records with links to EADs.
● Wisconsin has a collection sharing system for archives within the state to fourteen university campuses, but that process is managed through Ex Libris’ Alma/the shared ILS.
Centrally/collaboratively produced best practices, standards, or documentation Yes; EAD markup guidelines, primarily maintained by WHS: https://kb.wisconsin.edu/uwlss/ internal/page.php?id=71650) (This link requires authentication by a Wisconsin campus) Another maintained by University of Wisconsin-Milwaukee Archives (This is an internal document, but is available to all participating institutions).
The EAD markup guidelines include some information on how to contribute a finding aid, but institutions largely rely on personal contacts at the University of Wisconsin or Wisconsin Historical Society to set things up. Processes are not otherwise documented, and likely needs to be as they are adding new contributors. Each institution maintains its own documentation, and updates on their own schedule.
Standards Enforcement
A mix of standards enforcement and central normalization.
Their standards enforcement is based on EAD validation, so not many fields are required. If an institution puts a document on the test site and it’s not valid, they get an automatic email from the system that they need to correct an error. Descriptive standards compliance is the
responsibility of the institutions.
Because of how they emerged (see Organizational History), they are largely working with a consistent set of documents from the Wisconsin Historical Society. However, many of the documents were legacy descriptions sent out for vendor encoding without much metadata remediation or selection beforehand, and the vendor encoded very differently from an institution. Thus, some of the data is not really what you would expect in a finding aid. Services Offered
In the past, the Wisconsin Historical Society and University of Wisconsin--Madison worked with new contributors. The new contributor would visit in person to get set up, trained, and familiar with processes. They are transitioning to a new approach that doesn’t require so much WHS involvement. A new person is setting up documentation and onboarding processes for new contributors.