-
Notifications
You must be signed in to change notification settings - Fork 3
User Manual
This is a walkthrough of the program and how it functions.
- It takes resource identifiers separated by new lines or commas from ArchivesSpace as inputs, searches the ArchivesSpace database, exports EAD, MARCXML, Container Labels, or PDF files for the resources specified, cleans the EAD.xml files, and saves them locally.
- For XTF users, EAD.xml or .pdf files as selected by the user are uploaded to the XTF finding aid website/database and the program indexes just those records uploaded/changed.
Upon running the program, the user is met with 2 windows:
Input your username, password, and the ArchivesSpace API URL. Use XTF Version - check this box if you want to use XTF features (default is checked)
Input your username, password, the XTF Hostname, XTF RemotePath (where the EAD files are stored), XTF Indexer Path (the filepath to the indexer file), and the XTF Lazy Index Path (the filepath to the .lazy indexer folder for EADs or PDFs).
- A note about establishing XTF credentials. In our testing, we were having trouble connecting users with the remote XTF space. We solved this by adding individual user's IP addresses to secure protocols.
On the top right contains 4 radio buttons where users can select what export option they would like to use. The default is set to EAD. Additionally, a user must select which repository they would like to export from. The default is Search Across Repositories, but you can save a different repository clicking on the "SAVE" button.
There are 3 sections of options:
When a user inputs a resource identifier in the multiline text import (Large Box #1) listing them in either newlines or separated by commas, this button will search the ArchivesSpace database for resource identifiers that match the inputs. It will then take those it found and run them through a cleanup script, if set by EAD Export Options, and save them to a local folder called clean_eads by default.
EXPORT ALL will export all resources for the selected repository (or if you have "Search Across Repositories (Admin Only)" selected, it will do every repository for your ArchivesSpace Instance) that are published in ArchivesSpace.
This button allows the user to customize how they would like the EAD records to be exported. This includes setting the options to keep the raw ASpace exports and running the cleanup process on the exported EAD.xml records.
- Include unpublished components (default is false) - an ArchivesSpace exporting feature to include unpublished components from a collection
- Include digital objects (default is true) - an ArchivesSpace exporting feature to include digital objects that are attached to the resource and associated archival objects
- Use numbered container levels (default is true) - an ArchivesSpace exporting feature to number the container levels in the exported XML file (ex. <c01, c02)
- Convert to EAD3 (default is false) - an ArchivesSpace exporting feature to use EAD3 standard for export. Default is EAD2002
- Remove non-alphanumeric characters from filename (default is true) - remove all characters that are not numbers or letters from the exported filename
- Keep raw ASpace Exports (default is false) - keep the un-edited EAD.XML files that are exported from ArchivesSpace
- Set raw ASpace output folder - set the folder for where to keep un-edited EAD.XML files
- Clean EAD records on export (default is true) - run a series of XML cleanup (see Cleanup Options) on exported EAD.XML files
- Set clean ASpace output folder - set the folder for where to keep cleaned EAD.XML files
This button allows the user to select what sorts of cleanup they would like the EAD record to run through. The default is set to all.
-
Add Resource ID as EADID
- Takes the resource identifier as listed in ArchivesSpace and copies it to the element in the EAD.xml file. -
Delete Empty Notes
- Searches for every<p>
element in the EAD.xml file and checks if there is content in the element. If not, it is deleted. -
Remove (), [], {} from and Empty Extents
- Does 2 things. It deletes any empty<extent>
elements and removes non-alphanumeric characters from the beginning of extent elements. An example would be:<extent>(13.5x2.5")</extent>
. This would change to<extent>13.5x2.5"</extent>
. -
Add Certainty Attribute
- Adds the attributecertainty="approximate"
to all dates that include words such as circa, ca. approximately, etc. -
Add label='Mixed Materials' to containers without label
- Adds the attributelabel='Mixed Materials'
to any container element that does not already have a label attribute. -
Remove trailing . from langmaterial
- Removes the ending period on the element. -
Delete Empty Containers
- Searches an EAD.xml file for all container elements and deletes any that are empty. -
Add Barcode as physloc Tag
- This adds aphysloc
element to an element when a container has a label attribute. It takes an appended barcode to the label and makes it the value of the physloc tag. -
Remove Archivists' Toolkit IDs
- Finds any unitid element with a type that includes an Archivists Toolkit unique identifier. Deletes that element. -
Remove Archon IDs
- Finds any unitid element with an Archon unique identifier. Deletes that element. -
Remove xlink Prefixes from Digital Objects
- Counts every attribute that occurs in a<dao>
element. Removesxlink:
prefixes in all attributes. -
Remove Unused Namespaces
- Removes any unused namespaces in the EAD.xml file. -
Remove All Namespaces
- Replaces other namespaces not removed byclean_unused_ns()
in the<ead>
element with an empty<ead>
element.
- Open Cleaned EAD Folder - This button opens the folder where EAD records that have gone through the cleanup process are saved. You can customize this folder in EAD Export Options.
- Open Raw ASpace Exports - If a user has selected "Keep RAW ASpace Exports" in EAD Export Options, this button will open the folder where the raw ASpace EAD records are saved. You can customize this folder in the EAD Export Options
Within this frame, you can upload files to your XTF website, re-index any new or changed records, and select options for handling the upload and re-indexing.
This button will open another window in the GUI. It will display a list of files you can select by clicking on the ones you want to upload - or press CTRL A to select all of them. After selecting, you can "Upload to XTF" by clicking the button.
You can also select different options for the upload, including:
- Re-index changed records upon upload (default is true)
- Select source folder of records
- Change XTF Login Credentials - button that opens the XTF popup window
This button will open a popup (window) for users to select files listed on their XTF server to delete and execute an indexing of the files deleted. You can change the settings to not execute a re-index after deleting files, however this will not remove the appropriate lazyfile, making the file still appear on the frontend of XTF.
This button will take the Indexer file the user entered in the XTF Indexer Path field and run a command line to re-index any new or changed records. The commands run are -index -default
- Re-index changed records upon upload (default is true)
- Update .xml and .lazy files permissions to RW-RW-R (0664) (default is true)
- Select source folder of records
- Change XTF Login Credentials - button that opens the XTF popup window
On the top right contains 4 radio buttons where users can select what export option they would like to use. The default is set to EAD. Additionally, a user must select which repository they would like to export from. The default is Search Across Repositories, but you can save a different repository clicking on the "SAVE" button.
When a user inputs a resource identifier in the multiline text import (Large Box #1) listing them in either newlines or separated by commas, this button will search the ArchivesSpace database for resource identifiers that match the inputs. It will return the files according to the default directory or one specified by the user.
Allows user to specify options on how to export their MARCXML and what folder they want the records saved in.
- Include unpublished components (default is false)
- Remove non-alphanumeric characters from filename (default is true)
- Open output folder on export (default is false)
- Set output folder
Open the folder where MARCXML files are being exported to.
On the top right contains 4 radio buttons where users can select what export option they would like to use. The default is set to EAD. Additionally, a user must select which repository they would like to export from. The default is Search Across Repositories, but you can save a different repository clicking on the "SAVE" button.
When a user inputs a resource identifier in the multiline text import (Large Box #1) listing them in either newlines or separated by commas, this button will search the ArchivesSpace database for resource identifiers that match the inputs. It will return the files according to the default directory or one specified by the user.
- Note: the files returns are in .tsv format
This button allows the user to customize how they would like Container Labels to be exported. This includes setting the output folder for exports.
- Remove non-alphanumeric characters from filename
- Open Output - open the folder where container label files are being exported to.
- Set output folder: - Choose the output folder where you would like container labels to be exported to.
Open the folder where PDF files are being exported to.
!WARNING! - ArchivesSpace versions 2.6.0, 2.7.0, and 2.7.1 will not work. The program will tell you what version you are running on the WARNING label in this screen.
On the top right contains 4 radio buttons where users can select what export option they would like to use. The default is set to EAD. Additionally, a user must select which repository they would like to export from. The default is Search Across Repositories, but you can save a different repository clicking on the "SAVE" button.
When a user inputs a resource identifier in the multiline text import (Large Box #1) listing them in either newlines or separated by commas, this button will search the ArchivesSpace database for resource identifiers that match the inputs. It will return the files according to the default directory or one specified by the user.
This button allows the user to customize how they would like the PDF records to be exported. This includes setting the output folder for exports.
- Include unpublished components (default is false)
- Include digital objects (default is true)
- Use numbered container levels (default is true)
- Convert to EAD3 (default is false)
- Remove non-alphanumeric characters from filename (default is true)
- Open output folder on export (default is false)
- Set output folder
Open the folder where PDF files are being exported to.
- Clear Cleaned EAD Folder - deletes all files in the folder where cleaned EAD records are
- Clear EAD Export Folder - deletes all files in the folder where not cleaned EAD records were exported
- Clear MARCXML Export Folder - deletes all files in the folder where MARCXML records were exported
- Clear Container Label Export Folder - deletes all files in the folder where Container Label records were exported
- Clear PDF Export Folder - deletes all files in the folder where PDF records were exported
- Reset Defaults - Resets the settings for all available options, including folder locations. You have to restart the program to reset defaults.
- Exit - exits the program
- Change ASpace Login Credentials - a window to reset your ArchivesSpace credentials
- Change EAD Cleanup Defaults - same as Cleanup Defaults button above
- Change EAD Export Options - same as EAD Export Options button above
- Change MARCXML Export Options - same as MARCXML Options button above
- Change PDF Export Options - same as PDF Export Options button above
- Change XTF Login Credentials (XTF VERSION ONLY) - a window to reset your XTF credentials
- Change XTF Options (XTF VERSION ONLY) - change XTF options, same as above in XTF Frame: XTF Options
- User Manual - opens a new tab in your browser to the User Manual page
- About - shows what version of the program you are running and the "Check Github" button sends them to the Github repo page