Versions Compared

Version Old Version 91 New Version 92
Changes made by

Michelle Flinchbaugh

Michelle Flinchbaugh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Required for this procedure:

...

For other problems with the files Proquest FTP's to us, ask Michelle to call Proquest technical support at 877-408-5027 or 800-889-3358 (or email at tsupport@proquest.com or
http://support.proquest.com/ ) to find a solution.

Adding Supplements to the metadata in Excel and Moving them to the PDF Directory

...

  • Make sure all rights fields have the header dcterms.accessRights .

  • Save your sheet2 (you must be on it) as a .csv file. While on the "save as" screen, change the character encoding to UTF8  by using the tools drop-down, selecting web options, then encoding, and UTF8.

  • Note the dates in the Excel file. Close the csv in Excel, and open it with notepad. Use find and replace to change them to the YEAR-MO-DA format. Save and close.

...

  • Check that all departments are in the collection builder file. Sort and scan.
  • Check the rights field labels to ensure they are  dcterms.accessRights 
  • Check the author field label
  • Check that dates are in the year-mo-da format. After this step is done, do NOT open in Excel but import selecting "delimited" as type and "comma" as the delimiter. When you get to step 3, make sure ALL the columns with dates are set to TEXT.

Run the SAF builder (documentation here: https://github.com/DSpace-Labs/SAFBuilder) :

  1. Be sure the csv is closed in all programs.
  2. Put the .csv metadata file and all of the files to be loaded in the directory in the ETD directory.
  3. Open Ubuntu.  
  4. Use the command ls to list all the files in the (The directory should include all of the files that compose a work, including supplements, and a csv file with metadata in it. The directory must be in the directory mapped to Linux)
  5. Open Ubuntu.  
  6. Use the command ls to list all the files in the directory, and cd to change the directory to navigate to the directory with the safbulider.sh file. Use the cd command alone to go up a level in the directory. Remember directory names, file names and commands are all case sensitive.
  7. Run the safbuilder by typing "sudo ./safbuilder.sh -c etd/path to metadata file." For example, "sudo ./safbuilder.sh -c  etd/Oct2019etds/PDFs/ETDtempDspace_Oct2019Load.csv"would run the safbuilder on the metadata.csv file and all of the files in the directory with it. Note that the etd in the path must be lower case despite that it's upper case in windows. You can use the up arrow to cycle through previous commands so that you don't have to retype. When you push enter to run the command, you'll be prompted to enter your password.
  8. The program will make a bunch of text appear in the DOS window. If it doesn't, the program didn't run.  You probably made a typo when you typed the run command in. Try again, and be sure to type it all correctly. When the program successfully runs, it creates  a SimpleArchiveFormat directory within the directory that you ran it on. The SimpleArchiveFormat contains numbered subdirectories: Item_000/, Item_001/, Item_0002, etc. Each of those subdirectories should contain a dublin_core.xml file, a contents file, and all the files that consist of the work described in the metadata.
  9. When it's run correctly, in DOS window, the last line should indicate that ETDtempDspace.csv has been used 0 times, and that should be the only line with a "File:" error See below:

    A SimpleArchiveFormat directory should appear in your folder that the files and the csv file are in.
  10. If there is more than the one "File" error, there is something wrong. See below:

    These errors happen when the files in the folder and filenames in the csv file don't match. Determine if there is a problem that needs to be corrected by comparing your .csv file to the contents of your directory. If necessary, make the corrections, then delete your SimpleArchiveFormat directory, and run the safbuilder again. If you can't fix the problems, or don't know what's causing them, ask Michelle for help. If she's not there, you can copy and paste all the errors to Word by pushing the PrtScn and Ctrl keys together to copy your screen to the clipboard, and paste your screen into Word--if there are many errors, scroll through them getting them all pasted into Word.
  11. If other errors occur, it's usually because of a typo in the command/path. Try to run it again.

...