STEADYOverview, Functionality and Demonstration

What exactly is Steady?

Steady is an open-source software tool utilized to create EAD container lists

Used alongside AT to import container lists Relies on CSV file type Incorporates limited range of EAD

elements Some post-Steady clean up may be

required Web site: http://steady.heroku.com

Why use Steady?

Two instances:#1

○ Donors provide a container list as a spreadsheet

○ Enables efficient and effective editing of lists

#2○ Poor wireless coverage○ Enables archivist to edit container lists off line○ Several archivists may work on a collection

resource simultaneously

What does a Steady spreadsheet look like?

…. Like a Microsoft Excel spreadsheet

What are the tags?

series title series number series dates subseries title subseries number subseries dates file ID file title

file dates extent physdesc internal only restrictions conditions

governing access scopecontent

What are the tags?

note1 note2 instancetype container 1 type container 1 number

container 2 type container 2 number container 3 type container 3 number other extraneous

tags that are rarely used

REMEMBER: TAGS MUST CONFORM TO THIS SCHEMA.

What happens to the Steady spreadsheet?

Save as a comma delimited file type (make sure to save a separate version of the original Microsoft Excel file, for editing)

Upload the spread sheet into Steady Save as XML type Review and adjust (unittitle and unitid)

the XML file in Notetab, oXygen XML Editor, etc.

What happens to the Steady spreadsheet?

Import into AT Verify the adjustments (e.g., “Preliminary

Inventory to the…”) are correct Finalize and transfer the components

between AT resource records

When do I use it?

Consider RDE if… Adding consecutive

entries (some jumping around, but not a lot)

Other note types are needed (General Physical Description)

Diacritics or other complications may be faster to enter in RDE

Consider STEADY if… • Adding long,

consecutive lists (all entries will transfer to the same place in AT)

• Data can be converted to CSV (from Word, via Excel, etc.)

• All required notes are in the schema

• No notes at the file level

Takeaways Primarily an import tool, very similar to RDE Learning curve to STEADY

Mapping of column header less intuitive than RDEGetting the data into correct CSV type can be time-

consuming Can save time, but not always

Reduces copying and pasting fields in AT, but requires moving the data through several conversions

Mapping to the columns can be complicatedCSV/Excel can create challenges (dates, number

ranges, and diacritics)

So, how does Steady really work?

And now… a demonstration!

Create a CSV file.

Import the CSV File Into Notetab, oXygen XML Editor, etc.

Import the XML file into AT.

Search for the ‘Preliminary’ FA.

Check for errors or changes.

Merge ‘Preliminary’ FA with actual FA (see Nancy).

You have now imported a Steady spreadsheet into AT.