Section 9.2.1                   Project Name

Give your project a name. It is best to make the name descriptive. For example, a department name or record type. This will make it easier for production personnel to select the correct project.

Section 9.2.2                  Company

You may have different divisions within your company that run under different names, or you may be a vendor that processes records for many clients. Regardless of your organizations structure or if you are a vendor servicing multiple clients, enter the name of the company whose records will be stored in the project.

Section 9.2.3                  Image Sort Order

Images from the WIB apparatus and/or Mobile app are delivered to end users in WIB Review per the sort order defined for the project.

Section 9.2.3.1             Default Sort Order

The images are sorted in the following order by default, so they appear in the order of most important to least important. Importance is decided by which images have the greatest value or content combined with organizational hierarchy.

Manifest, Standard, Stadium, Content, Divider, File, Tab, Document, front, right, back, left, top, aerial

Section 9.2.3.2            Custom Sort Order

Some projects may require a custom sort order, or you may prefer to see the images in a different order. To change the order of the images, type each image name in the order you would like them to appear separated by a space. Do not include commas.

Section 9.2.3.3            Chronological Sort Order

You may prefer to see the images in chronological order (the order in which the images were captured). Turn on Chronological order to view images in the order they are captured.

Section 9.2.4                  Description

Adding a description to your project is optional but does supply more information that could be helpful in the future.

Section 9.2.5                  Hidden Collection

You can hide a project from production. This is useful when setting up a project that you do not want users producing records in. You can complete the setup and when ready make the project visible to end users.

Section 9.2.6                  Collections (Owned by Project Name)

It is suggested you create a Taxonomy before creating a Collection for a Project. Collections require a taxonomy before they are available for production. Please Refer to Configuration Management, Automation, Taxonomy for instructions on setting up a Taxonomy.

Section 9.2.6.1              Collection Name

Give your collection a name. It is best to make the name descriptive. For example, a department name or record type. This will make it easier for production personnel to select the correct collection.

Section 9.2.6.2             Project

The Project is selected by default when you create a collection from within a Project.

Section 9.2.6.3             Taxonomy

Select the Taxonomy you want applied to the records in the Collection.

Section 9.2.6.4             Description

Adding a description to your project is optional but does supply more information that could be helpful in the future.

Section 9.2.6.5             Hidden

You can hide a collection from production. This is useful when setting up a collection that you do not want users producing records in. You can complete the setup and when ready make the collection visible to end users

Section 9.2.6.

1       

Add Tags to a Collection

After a collection is created, you can add tags for the Review process. Select the Tags tab, then click the Add Tag button to add a user-defined tag. Tags consist of a name, description, Tag Color, and Text Color. These tags are then available to users as a drop-down menu on the Tag Tile during Review. Tags will appear in Review with the same tag color and font color defined under the Collection.

Section 9.2.7                 Define Hierarchical Capture

Hierarchical Capture allows the export to identify images that are associated. There are 3 levels available: Container, Parent, and Child. Drag images are associated with the Container to the Container level, images that are Parents and their associated Child images. Below is a typical Hierarchical Capture definition.

Section 9.2.7                 Content Type Definitions

Content Type Definitions allow for identifying the Hierarchy for exporting the Metadata in XML format. For each image type, the user can define the Content Type, which is included in the XML at the Container and Parent nodes. Below is a standard Content-Type Definition.

Section 9.2.9                 Reference Collections (Roadmap)

Reference collections managed by another project can be added to any project. The billing is associated with the original Project. This allows departments and later projects access to records without exporting, importing or reprocessing records.