Differences

This shows you the differences between two versions of the page.

--- new_objects [2018/04/03 17:55]
128.119.168.9 [1. Preparing metadata]
+++ new_objects [2022/04/01 17:27] (current)
jeremy
@@ Line 1: / Line 1: @@
 ====== Adding new objects to Credo ======
@@ Line 8: / Line 9: @@
 ===== 1. Preparing metadata =====
-There is a script used for preparing metadata for ingest that lives on r:/credo/metadata/utilities/mods/mods called mods.exe. It is easiest if you put a ticket into Systems to have this script moved to a folder in your PATH. They will know what this means. Unfortunately, this can only be done by someone with admin privileges to your computer.
+There are two different tools that can be used to prepare metadata for Credo, a command line interface (CLI) and a desktop application. The desktop application is the simplest and recommended method. The CLI is considerably more powerful and can accomplish a bunch of other metadata maintenance tasks. The full documentation for the CLI lives at [[mods_command_line_tool|its own page]].
+==== Desktop app ====
+To set it up:
+**Windows**
+) Go to r:/credo/metadata/utilities/mods_UI/Windows and copy the entire folder named 'MODS' to somewhere in your profile, e.g. your Documents folder.
+) Enter your local copy, right-click on the MODS.exe file, select "Send to" and select Desktop. This should create a shortcut to your local version that you can access on your Desktop.
+) Launch the app by double-clicking the shortcut.
+**Mac**
+) Go to r:/credo/metadata/utilities/mods_UI/Mac and copy MODS.app to your local Applications folder (or anywhere locally on your Mac).
+) Launch the application by double-clicking MODS.app.
+To use the app, press the "Open" button to browse to a folder you want to check. Once the folder is selected (the full path should appear in the bar at the top), press "Run" to check the files. If the files have no errors, the app will automatically add IDs, so no need to do an extra step. If there are errors, the app will list the files and errors. Next to each error is an open button which will open that file in your default application so you can fix. Once fixed, select "Rerun" and hope for the best!
+:!: The QA application **must** be run on every MODS file before it is ingested into Credo. It's also probably wise to run again if items have been edited.
+==== CLI ====
+The CLI program is stored in r:/credo/metadata/utilities/mods/mods and called mods.exe. It is easiest if you put a ticket into LTS to have this script moved to a folder in your PATH. They will know what this means. Unfortunately, this can only be done by someone with admin privileges to your computer.
 This script can do a whole bunch of mildly useful things but for the purpose of preparing metadata, it:
@@ Line 16: / Line 43: @@
 :!: The script **must** be run on every item before it is ingested into Credo. It's also probably wise to run again if items have been edited.
+To prepare a batch of files for ingest you will need to run two separate commands:
+''$ mods -c [folder]''
+This will check all files in a specified folder for errors. If the script returns to the prompt without displaying any information, the files in the folder are ok.
+''$ mods -Iwu [folder]''
+This will add the IDs and URLs to the MODS records. Once both of these commands have been run, the files are ready for Credo.
+===== 2. Uploading to Credo =====
+Once the files are prepared, they need to be uploaded to Credo.
+  - **Log into the Credo server via SFTP**. The server name is ''credo.library.umass.edu'', the username is fedora, and Aaron R. will give you the password.
+  - **Upload the metadata and object files to the appropriate folder**. If you are adding to an existing collection, add the files to the pre-existing folder. If you are creating a new collection, add a top-level collection folder, upload the files there, and follow the [[new_collections|steps to add a new collection to Credo]].
+  - **Add a copy of all the metadata files for the objects you would like to ingest into the 'ingest' folder.** Ingest runs once an hour and will only add 100 objects per hour. You will know an object has been ingested if the file disappears from the ingest folder.
+-) It's generally easiest to drag actual metadata files into the ingest folder but it's worth knowing that the ingest process doesn't care, as long as there is a file with the object PID and the extension '.xml'. The file can be empty or something completely different. Credo trivia!
+==== Adding video/audio captions ====
+  - Generate a .vtt file of the captions for the video you wish to add captions for.
+  - Name the file with the same PID as the corresponding video: [PID-reference.vtt, eg. mums1093-s10c-i005.reference.vtt]
+  - Upload the .vtt file along with the access and archival files and the xml. So you should have a total of 4 files for each video:
+  * mums1093-s10c0-i005-001.access.mp4
+  * mums1093-s10c0-i005-001.archival.mov
+  * mums1093-s10c0-i005.reference.vtt
+  * mums1093-s10c0-i005.xml
+==== Manually adding PDFs (instead of the automatically generated ones) ====
+  - Upload the PDF that corresponds with the item
+  - Name the file thusly: [PID.reference.pdf, eg. mums1156-s01-i001.reference.pdf]
+  - Upload PDFs to appropriate folder
+  - Ingest (or re-ingest) the corresponding XML records

scua

User Tools

Site Tools

Differences

Page Tools