On this page:
Project templates
JSTOR Digital Stewardship Services offers project templates as a way to start your project with guidelines. Project templates consist of pre-built metadata schema, meaning the field labels are created, the field types designated, description text added, and the position number of the fields in the item panel defined.
For pre-built Linked Authority fields, suggested resources are already linked to use at your preference. Templates also come with a pre-built full cataloging form, representing every field in the metadata schema.
Project templates are entirely editable to create your custom fields and cataloging forms, so you can always use a template to define your own metadata fields if you’re unsure where to begin.
Project templates include:
- JSTOR Template - Contains all of the metadata fields available when publishing a variety of work to JSTOR.
- Seeklight Template (Tier 3) - Based on the Dublin Core metadata schema, a schema for AI metadata generation with JSTOR Seeklight that provides all available Seeklight fields pre-enabled.
- Dublin Core Template - Based on Dublin Core fields, this template is useful for describing archival and print materials.
- Visual Resources Template - Based on VRA Core, these fields are often intended for visual resources collections, but can be modified to fit other cultural heritage object collections.
- Archivision Template - Based on Archivision fields, this template is recommended for institutions subscribed to Archivision and interested in hosting the content in JSTOR Stewardship. Visit Archivision.com to learn more about the base and modular collections or to obtain a copy of the data and images for uploading if your institution is subscribed.
You can configure template fields, field types, and descriptions by following the instructions in Managing project fields.
Creating a new project
To create a new project:
- Log into JSTOR Digital Stewardship Services with an account that has Institutional Admin permissions.
- Not an admin yet or have questions about managing user access? Contact JSTOR Stewardship Support.
- On the Home page, select Create a new project.
- Tier 3 participants may also choose to Upload media and generate metadata with JSTOR Seeklight. See JSTOR Seeklight: Overview to learn more.
- Select Create new from a pre-defined schema template to start with one of the available metadata schemas and select Next to continue.
- Alternatively, select Copy fields from an existing project to start with the metadata fields, cataloging forms, publish targets, and field mappings from an existing project. See Copying an existing project for more information.
- Or, select Create fields from a spreadsheet to build a collection step-by-step by uploading a spreadsheet containing your metadata.
- Choose one of the available metadata schemas to preview the schema's fields, field types, and descriptions and select Next to continue.
- Tier 3 participants can also preview which fields are compatible with JSTOR Seeklight's metadata generation.
- Choose a title and optional description to identify your project in JSTOR Stewardship.
- Note that a "project" refers to content in JSTOR Stewardship that may be published as a collection to one or more publishing destinations. Your project title and description will only appear within JSTOR Stewardship. You'll choose a collection title and description when setting up a publishing destination.
- Select Next to finish creating your new project and visit the project settings page.
Copying an existing project
To facilitate the process of creating projects, administrators can also copy a completed project. This will automatically establish the fields, including the types, descriptions, and positions, as well as cataloging forms, publishing targets and field mappings. This is especially useful if the project configurations are similar, but the content must be kept separate.
Though you can copy the built structures of a project, field values are not copied. Also, fields which link to an integrated or external source in the project from which you copied will not retain their sources in the new project. Administrators will need to add the appropriate sources to the specific linked fields from the Fields tab.
While it is useful in some instances to copy a project and re-use the publishing target, other projects may need to be established with a new target. Before you begin adding any content, go to the Targets tab and verify that this copied target is the intended publishing environment for your new, copied project. If it is not, select the target and remove it, then create your new target from any of the available target types. Remember to map your new project’s fields to the target fields, as well as add a collection description and representative image.
To copy an existing project:
- Log into JSTOR Digital Stewardship Services with an account that has Institutional Admin permissions.
- Not an admin yet or have questions about managing user access? Contact JSTOR Stewardship Support.
- On the Home page, select Create a new project.
- Select Copy fields from an existing project select Next.
- Choose from your existing projects to preview the metadata fields, publishing targets, and cataloging forms your project will start with and select Next.
- Choose a title and optional description to identify your project in JSTOR Stewardship.
- Note that a "project" refers to content in JSTOR Stewardship that may be published as a collection to one or more publishing destinations. Your project title and description will only appear within JSTOR Stewardship. You'll choose a collection title and description when setting up a publishing destination.
- Select Next to finish creating your new project and visit the project settings page.
Renaming a project
To rename a project:
- In your project, select Project Settings.
- In the Overview tab, select Edit name and description after the project name.
- Once you've finished updating the project name and/or description, select Save.
Deleting a project
To delete a project:
- First, suppress all items published to targets. See Suppressing and deleting items for more information.
- If you'd like to delete a project that has been published to Omeka, exposed as OAI, or harvested for DPLA, additional steps are required. Please contact JSTOR Stewardship Support to learn more.
- In your project, select Project Settings.
- Select Delete project and confirm your selection by checking the “All items in the project will be deleted" checkbox and choosing Yes, delete.