Section 9.2.6 New Collection

Section 9.2.6 New Collection

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

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                 Add Attributes to a Collection

Add the attributes for the Collection. Attributes can be filtered to include only those applicable to the Collection. Go to the Attributes tab on the Collection Page and select Add Attributes. Select each attribute that will be used for the collection of data extraction.


Section 9.2.8                 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.

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.10                 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.



    • Related Articles

    • Section 9.2 New Project

      Section 9.2 New Project Prior to setting up a project you will need to set up the attributes. Please refer to the following section of the Manual: Configuration Management, Attributes. Section 9.2.1 Project Name Give your project a name. It is best ...

    • Section 12 Security Management

      Security Management Security Management allows Administrators to set up users or groups, and policies and scopes, which, combined, become a Security Policy Definition (SPD). Policies are vital for keeping proper access rights to your most sensitive ...

    • Section 10.2.5 Taxonomy

      Section 10.2.5 Taxonomy A Taxonomy in WIB is the combination of lists and regular expressions and how they are used to classify records. Section 10.2.5.1 Overview Explains what a taxonomy is and how it is used in WIB Review. Section 10.2.5.2 New ...

    • Section 9 Project Management

      Project Management A Project holds the overall design of the system. This area allows the Workspace Administrator to manage Projects and their parts (entities). A Project has the following entities: collections, attributes, automation, and workflow. ...

    • Section 1 Getting Started

      Previous Article: Getting Started The Review Platform for What’s in the Box is designed to provide end users access to the photographs of records with the extracted data configured in the Platform. This allows for users to use the analytics, auto ...