Journals that are defunct (have ceased publication) are archived in UVicSpace to preserve the content. The journal's site is then deleted.
Journals are archived using this structure:
The journal community page should include the information about the journal from its website, e.g.:
When recording metadata for the cover page and submission form, work from the PDFs rather than from the journal website. Formatting and special characters are often missing from the website.
Cover pages for archived journal articles are the same for faculty publications, with these exceptions:
Complete the submission form following the steps for faculty publications, with these exceptions:
Items can be added one at a time using the submission form, but it's best to upload them in bulk. This is a two-step process: first, the metadata is imported in bulk, then PDFs are added to each item as bitstreams.
Archiving articles using bulk metadata import is a two-step process. First, the metadata is imported from a CSV file, then the bitstream(s) for each item are uploaded manually.
Export a model CSV file by exporting the metadata from one of the issue collections.
Note: The first row of the CSV file contains the labels for each field, corresponding to the fields in the submission form. They are labelled with the Dublin Core labels, e.g., dc.description.abstract corresponds to the Abstract field in the submission form. The first column, labelled id, must remain intact. It contains the unique id that UVicSpace assigns to each item. Each row in the spreadsheet represents an item, so each item’s metadata must be entered on a new row, and an item can only occupy one row.
Enter the metadata for the new items, referring to the example item as necessary for how to format the data. Items from multiple issues can be entered on the same spreadsheet: the value in the Collection column determines which collection the new item is added to.
Id: Enter + in each row. This tells the system to create a new items.
Collection: Enter the numbers at the end of the permanent URI for the community, including the slash: e.g., for https://dspace.library.uvic.ca/handle/1828/3853, enter 1828/3853.
dc.contributor.author (Author): Enter author names as Lastname, Firstname. Separate multiple authors with double pipes ||.
Note: Check whether each author has items in UVicSpace already and use the authoritative version of their name. This helps prevent the system from generating multiple records for each author.
dc.date.accessioned: Leave this blank.
dc.date.available: Leave this blank.
dc.date.issued: Leave this blank.
dc.description.abstract (Abstract): Enter the abstract. Delete any line breaks.
dc.description.provenance: Leave this blank.
dc.description.reviewstatus (Peer Review Status): Enter Reviewed or Unreviewed.
dc.description.scholarlevel (Scholarly Level): Enter the scholarly level from this list:
dc.identifier.citation (Citation): Enter the citation in APA format, omitting italics.
dc.identifier.uri: Enter the DOI. Separate multiple values with double pipes ||. Do not include URLs to the journal's website, since they will soon be broken.
dc.language.iso (Language): Enter en for English. For other languages, enter the appropriate ISO 639-1 code.
dc.publisher (Publisher): Enter the publisher (journal) name. If a journal's name has changed over time, use the current (authoritative) name.
dc.rights.uri (part of Creative Commons License): Enter the URI for the appropriate Creative Commons license, if applicable, e.g., http://creativecommons.org/licenses/by-nc/4.0/.
dc.rights (part of Creative Commons License): Enter the name of the appropriate Creative Commons license, if applicable, e.g., Attribution-NonCommercial 4.0 International.
dc.subject (Keywords): Enter keywords in lowercase (caps when required), separated by double pipes ||.
dc.title (Title): Enter the title in sentence case.
dc.type (Type): Enter the item type from this controlled list:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check all the metadata carefully for accuracy and consistency.
Note: Items submitted via batch metadata uploads do not go through the usual workflow, so they are entered directly into the repository. Ensuring that the metadata is accurate at this stage is very important!
Best practice is to import metadata in two steps: first, validate the metadata, then do the actual import.
To import the validated metadata, begin a new process.
Upload at least one file/bitstream for each item. The thumbnail and license file will be generated automatically.
Details to come: