All posts by afocke

Schema transition underway – see the year’s rough schedule

TARO repositories have been sorted into three groups for the purposes of working through schema conversion process.

Each repository will be worked with individually to ensure their documentation and training needs are met.

Scroll down to see what to expect and where your repository is grouped, and please know we will be in touch with your repository to discuss this process and the timing.
Questions right now? Contact Amanda Focke

  • Group A – Spring / early Summer 2016: repositories already creating schema compliant XML with software such as ArchivesSpace, ArchivistsToolkit, CuadraStar, Archon.
  • Group B –   Summer – Fall 2016: repositories encoding by hand in XML editor of some sort, significant current staff experience and documentation
  • Group C –  Winter – early 2017: encoding by hand in XML or text editor, little or no current staff experience and documentation

TARO workflow steps for repositories moving to schema compliant XML submissions, 2016

What to expect: Overall, each repository should expect the conversion process to take about a week, with the work happening via a script run by Minnie Rangel, and the repository not having account access during that time. After that, the repository can submit edited or new finding aids as long as they are schema compliant, and guidance will be provided on how to do that.

  1. Scheduling the conversion, repository by repository

Minnie Rangel and Amanda Focke  to schedule conversion with repository at a convenient time.

  1. Blocking repository account access during conversion

Tuesday of the scheduled conversion week, the repository’s account access is blocked by Minnie to prevent any submissions during the conversions.

  1. Schema conversion of existing files at TARO
    Wednesday of the scheduled conversion week, Minnie runs the dtd-to-schema conversion script on the repository’s existing files in TARO. This may take 2-3 days depending on the number and size of the files. (For example, 800 files might take 2-3 days.) At the end of this process, all the XML files on TARO’s server for this repository will be schema compliant and valid, with no need for the repository to take further steps on them, unless there was an error (see below for further info on errors). The HTML webpage for the finding aids that researchers see online will not have changed at all.
  2. Repository to download their dtd files and new schema files for local backup.

Repository will log in to their TARO account in the usual manner as access will have been restored, and use the secure-shell client’s tools to download all their files. The old DTD XML will be in one folder and should no longer be used for current finding aid editing, only as an archived copy. The newly created schema compliant files can be used for editing if needed.

  1. Error correction on schema compliant XML

In the event of any errors, Minnie will supply a list of such errors which will be helpful in correcting them.

  • Please note that the correction of these errors is required but can be done at the convenience of the repository, since the finding aid seen by users is still the HTML as generated by the old DTD file.
  • Advice and troubleshooting will be available from the TARO Outreach and Committee, and possibly other TARO committee members as needed.
  1. Any new or edited XML submitted will need to be schema compliant and valid

Going forward from your conversion, any edits to files, such as for updates to a finding aid, will need to be submitted as a valid schema compliant XML file in order for it to process correctly and show online as HTML. You will be given the documentation and other info needed in order to do this using essentially the same workflow you already have, it is not a huge change.


 

A note about groups — if you think your repository is in the wrong group, or you don’t see your repository at all, please contact Amanda Focke. The groups were made based on survey responses in Fall 2015 or by email / phone in early Spring 2016.

Group A: roughly scheduled for Spring / early Summer

African American Library at the Gregory School (AS)
Baylor University (CuadraStar)
Rice University, Fondren Library, Woodson Research Center (AS)
Texas General Land Office Archives and Records (AT)
Texas A&M Corpus Christi (AS)
Texas A&M University Cushing Memorial Library (Archon)
University of Houston Libraries, Special Collections (Archon) University of North Texas Archives (Archon)
Vietnam Center and Archive, Texas Tech University (AS)

Group B: Roughly scheduled for Summer / early Fall

Austin History Center, Austin Public Library (NoteTab)
Austin Presbyterian Theological Seminary (Notepad++)
Daughters of the Republic of Texas Library at the Alamo (Oxygen) Harry Ransom Humanities Research Center, University of Texas at Austin(Oxygen)
Houston Academy of Medicine-Texas Medical Center Library, John P. McGovern Historical Collections and Research Center (Oxygen) Houston Public Library, Houston Metropolitan Research Center (limbo between AT/AS)
San Jacinto Museum of History (Oxygen)
Southern Methodist University (Oxygen)
Stark Center, University of Texas at Austin (Notepad++)
Stephen F. Austin University (limbo between Archon/AS)
Tarlton Law Library, University of Texas at Austin (Oxygen)
Texas State Library and Archives Commission (Oxygen)
Texas Tech University Southwest Collection/Special Collections Library (Oxygen)
Texas/Dallas History and Archives Division, Dallas Public Library (NoteTab)
Texas State University (Oxygen)
The University of Texas at Austin. Alexander Architectural Archive (Oxygen) –CONVERTED FEB 2016 IN TARO PILOT WORK
The University of Texas at Austin. Benson Latin American Collection (Oxygen)
The University of Texas at Austin. Dolph Briscoe Center for American History (Oxygen)
Truman G. Blocker, Jr. History of Medicine Collections,
Moody Medical Library, University of Texas Medical Branch (Oxygen)
University Archives and Special Collections The University of Texas at Tyler (limbo between Archon/AS)
University of Texas Arlington Library, Special Collections (XMetal)
University of Texas San Antonio (Oxygen)

Group C:  early 2017

Tyrrell Historical Library (Oxygen)
Concordia University Texas Historical Online Collection (Oxygen)
Lamar University’s Archives and Special Collections (NoteTab)
Robert E. Nail, Jr. Historical Archives at Old Jail Art Center (NoteTab)
San Antonio Municipal Archives
South Texas Archives at Texas A&M University-Kingsville (Oxygen)
Texas Woman’s University, the Woman’s Collection (Oxygen)
University of St. Thomas Archives
University of Texas El Paso (Oxygen)
University of Texas M.D. Anderson Cancer Center (Oxygen)
UT Health Science Center San Antonio
UT Human Rights Documentation Initiative


 

Scheduling the transition to schema compliance in 2016

Dear fellow TARO members,

Our progress towards updating TARO files to schema compliance continues.

Thanks to your participation in our Fall 2015 survey regarding your repositories’ methods for creating EAD finding aids, we have been able to group our TARO repositories into 3 groups for the purpose of scheduling each repository’s schema updates in 2016:

  • Group A includes repositories already creating schema compliant finding aids (for example those using collection management software which exports schema compliant EAD). This group would go through the schema transition first (Spring 2016).
  • Group B includes repositories creating dtd compliant finding aids with significant staff experience and workflow documentation. This group would go through the schema transition second, with assistance from members of the TARO team (timeframe to be determined).
  • Group C includes repositories creating dtd compliant finding aids with less staff experience and workflow documentation, as well as those who are close to creating dtd compliant finding aids and who need training or other support to get started. This group would go through the schema transition third, with assistance from members of the TARO team (timeframe to be determined).

About half of TARO repositories responded to the survey which allows us to sort repositories into these groups for planning purposes.
Our next step will be to follow up in the next two weeks with the repositories who did not respond so we can plan the year’s schema compliance work accordingly. We do realize that in some cases where repositories did not respond, the contact email we have could have been out of date, and we will do our best correct that situation.

Questions about this schema compliance planning process? Contact Amanda Focke at afocke@rice.edu.

Otherwise, stay tuned!
Thanks,
Amanda
TARO Steering Committee Co-chair
TARO blog for public news Wiki as working committee records

Upgrading to schema compliance in 2016!

As promised in August 2015, we at TARO have been working diligently on preparing our system to move to the more modern format of schema-compliant EAD.
We have conducted our pilot project for moving to schema-compliance.

We will start with volunteers for early conversion with the rest following as training and support allows. No one will be rushed into conversion.
We will contact you in January 2016 to discuss this process, answer your questions,  and hear when your repository would consider participating.
A specific TARO contact person will be available to you for questions and assistance throughout this process.

We will be ready starting in January 2016 to begin working with each repository one at a time to:
1.) Convert the repository’s existing files which are on TARO over to schema compliance. TARO’s Minnie Rangel will use an automated process and then work with repositories on manually following up on any errors (at the repository’s convenience, or at the time when the repository wishes to reload a given file for content changes). The time needed for this will vary from repository to repository, but shouldn’t be significant, and is not on a particular deadline.
2.) Give you the information you need in order to start submitting schema-compliant files to TARO from then on.
(You may still submit dtd-compliant files all the way up until the time your repository converts to schema compliant submission.)

We look forward to working with you on this and appreciate your participation, as this step is the basis for any additional TARO improvements.

Sincerely,
Amanda Focke, on behalf of the TARO Steering Committee

TARO changes behind the scenes this Fall

Fellow TARO members –

TARO is preparing to update its systems to accept schema compliant EAD.  

This is very exciting news! But what does this mean for you?

Updating to fit the modern environment

Since TARO’s beginning in 2000, repositories have been asked to send in EAD xml files of the “dtd-compliant” variety. Over time, the larger archives community has moved to what is known as “schema” compliant format. The difference between dtd format files and schema format files is relatively minor in terms of how we encode our finding aids, and will likely not be apparent to researchers browsing and searching finding aids.

More importantly, any design updates TARO needs will depend on our files being in schema format. At the same time, more TARO repositories have moved to using collection management software such as Archivists Toolkit, Archon, CuadraStar, or ArchivesSpace — all of which only export schema compliant EAD.  Currently those repositories have a variety of challenges in continuing to contribute to TARO in its current set up.

Clearly, TARO needs to shift into schema-compliance so that:

  • Our EAD is in alignment as we move forward with much needed upgrades to TARO’s infrastructure
  • repositories can have an easier path to participation in TARO, no matter how they create their finding aids

How will this work?

Most of TARO’s finding aids will batch convert seamlessly to schema-compliance without the  need for any additional work by TARO member repositories. However, some of our finding aids will require hand-encoded updates to work with the new system.

In Fall 2015, the TARO Steering Committee will conduct a pilot project that will convert a sampling of DTD-compliant TARO finding aids to schema-compliance. Based on the findings of this pilot project, we will evaluate what portion of our finding aids will require this attention, then create training and documentation for hand-updating existing finding aids. In addition, we will make tutorials that explain the installation steps for the schema-compliant EAD template to be used as members submit new finding aids. A schedule for the transition to schema-compliance will be released to TARO members after the conclusion of the pilot project and an evaluation of members’ need for assistance with hand-encoded updates to their EAD.

How will you know what is going on?

Should I keep submitting TARO finding aids right now?

Yes – please do! The only downtime for submitting your finding aids will be during the time we arrange with you to use the script to edit your files.