Project Start-up Checklist

By Sandra Schloen, December 2017

(For Project Administrators)

New OCHRE projects are set up in consultation with the OCHRE Data Service. A new project is provided with a Project Administrator user account which has full access to the OCHRE project. The purpose of this checklist is to guide a new project administrator through the steps needed to successfully get up and running in OCHRE.

By convention, new project setup will include:


Step 1: Project Preferences

After logging into the project, pause long enough to add a project Description on the Information tab of the Project pane.

Next, check out the Project Preferences and adjust them if necessary. 

Project Preferences

Step 2: Users

Note that the Linked Items Find-item-by-Name search is case sensitive. If you find the needed Person, switch to the Checklist Display format, select the required Person in the Query Results list, and use the checklist-link button highlighted above to insert the item at the selected context in the navigation pane.

Sort a list of items in a heading or hierarchy 

PLEASE NOTE! THE ORDER OF OPERATIONS IS IMPORTANT!

Step 3: Create a Project Taxonomy

Under the Taxonomy category, you will find the Project taxonomy that was initialized by the OCHRE Data Service on setup.

To re-use values, and by implication to align properties to some extent from other projects, in particular the master OCHRE project, follow these steps to find and link the desired properties. 

To find the value Coin, for example: 

Select one instance from the list of Query Results (if any). Generally, you will want to use the instance that does not have another project's prefix; this will be the generic instance in the OCHRE master project. Flip the Display format to the Checklist option, then check ON the instance you wish to select.

From an appropriate context in your project's Taxonomy (that is, the context in which you wish to insert the new item), use the Check-Link tool on the tool bar to insert the checked item into the taxonomy. 

Repeat as necessary! While this process requires a little extra time to set up, there is great collaborative value in sharing common properties with other projects, and also makes moot the need for Thesaurus entries for these items (we are reusing the very same item, so it does not have anything to which it needs to be made equivalent).

Step 4: Create Predefinitions

Under the Predefinitions category, create predefinitions based on your project’s taxonomy to provide templates and default values for data entry. 

Step 5: Create a Project Chronology

Under the Periods category, create a hierarchy for detailing your project’s chronology (or borrow one from another project).

Step 6: Create Locations & Objects

Step 7: Add Resources

Under the Resources category create hierarchies in which to organize your project’s images, PDFs, etc. 

If you have existing collections of resources, consult with the OCHRE Data Service regarding the possibility of importing large batches of external files. If the names of the external files contain the names of corresponding OCHRE items, then links from the item to the resource can be made on import. For example, a photo of “Item 101” can be automatically linked to the item on import if its file name contains the item name (e.g. “Item 101.jpg”, “Item 101 a.jpg”, Item 101_notes.pdf, etc.).

Check out these other wiki articles on Importing resources and on using the Drag and Drop Import option to insert smaller batches of images.

Step 8: Set up Geospatially-Enabled OCHRE (if applicable)

We recommend that you review the information available on Mapping Tools to get a general sense of what is involved in setting up Geospatially-Enabled OCHRE (GEO). You may also want to consult with the OCHRE Data Service specialists before beginning this step.

Specifically, you will want to:

Step 9: Configure Text Settings (if applicable)

Projects that are doing philology will want to initialize additional settings.

On the Project, Preferences, Tools page, link in any dictionaries or writing systems that are relevant for your project. Not only does this make them available for automatically importing texts, but it also helps speed up the loading of texts for Views and other kinds of analysis.