This article contains a glossary of terms used in the CollectionPro system. The glossary is intended to facilitate the use and understanding of the system for both new and more experienced users.
API (Programming interface)
Enables the integration of CollectionPro with other systems and the automatic exchange of data between them.
Asset
A digital file, means a digital version of something – it can be a document, photo, video, audio recording or anything else stored on a computer or other electronic device. Additional information about a file is called metadata.
Collection
Collections are like personal folders for collecting records. They can be turned into presentations, shared with others and used to download files. Collections can be structured hierarchically.
Data model
Object types and masks are central components in the structure and operation of the database. ‘Object type’ is practically a way to categorize different records or information in the database – for example to separate images from texts or videos from documents. The ‘mask’, on the other hand, defines how certain types of data are displayed and edited, i.e. it decides which fields are visible and how they are arranged.
These components, i.e. object types and masks, are defined in the ‘data model’. A data model is like a plan for the architecture of a database, which tells how data is stored, organized and processed.
It is also important to understand that systems often have a separate ‘development environment’ alongside the actual, actively used environment. The current data model (the one that is used now) and the data model to be developed (to which changes are made) are kept separate. This means that you can make and test changes in the development environment without affecting the operation of the current data model until you are ready to implement the new changes, i.e. ‘activate’ them.
Detail view
The Detail view is the part of the user interface that presents all the detailed information of a file or record, i.e. the metadata. This view is located on the right side of the user interface and is shaped like a sidebar. Users with the necessary permissions can see all the information and, when needed, proceed to edit it in the editor.
Lists
The Lists view is used to manage all object types and their associated records. Here you can find, for example, vocabularies and thesauruses. The use of lists requires the system permission “Manage lists”.
Mask
Masks are used to display and edit data fields in a record. The mask is a key part in the management of the rights related to the fields of the system. It determines which data fields of the record can be changed and whose content is only displayed. The mask can also be used to set the order of the fields and determine whether the data fields are displayed on tabs, panels or grouped.
At least one mask must be created for each object type (the first one is automatically created) and set as the default mask. Only one default mask can be defined for each object type. The default mask is used to decide which mask is used to display search results and details in situations where the user has rights to more than one mask (e.g. through different group memberships). If multiple masks are available, the user can switch between the masks in the info and editor views.
Metadata
Information that describes a file. This can be IPTC, EXIF ​​or XMP information stored inside the file, such as shooting date, photographer, copyright information. This can also be information internal to the system, such as the date of upload, the user who uploaded the file, and various classifications such as tags. Most search functions are based on metadata.
Pool
Pools are like folders where you can store your files and records. Different user permissions can be set for each pool, so you can define which user groups can access which record.
Primary object type
The primary object type refers to the database record or records that reflect the main content or central contents of the database. It represents the most important, perhaps the most fundamental data elements in a database. The classification as primary is based on the meaning and content of the information in the database, and not so much on the technical implementation. For example, a photo, video or document can be the primary object type in the database. These primary object types can be refined and extended using secondary object types that provide additional information or details about the primary records.
Record
The record is CollectionPro’s reference to the file. The record stores all system internal metadata, tags, album links, ratings, license information and person information. The record also contains a thumbnail of the file and a link to the file so that the file can be downloaded. One record is automatically created for each file. People also have their own person records that contain the person’s information.
Record version
The status of a record after saving. Each time a record is saved, a new version of the record is created.
Secondary object type
Secondary records are pieces of information that provide additional information or details about primary object types. For example, when talking about a photograph (the primary object type), secondary records might contain information about the photographer, keywords, and other relevant information. This additional information helps to better understand and classify the primary object type. Users can search, edit or delete these secondary records using special lists.
Tag
Tags are a type of label that can be attached to records. They can be used, for example, to monitor and describe various work phases, such as “editorial” processes. In addition, tags can be used to restrict or enable users’ access to certain records. As an example of this, publishing in the Finna system can be controlled by defining suitable tags for the record.
User
Accounts with access to CollectionPro. Users can be created under Rights management > Users.
Version control
A way for the system to track and manage different versions of files over time, allowing reversion to earlier versions when necessary.
Web platform
CollectionPro’s publishing interface for external users and targeted target groups such as personnel. In the web platform, users can browse, search and download files. The web platform gets its own fixed address and can be completely public or behind a login form. Files are published to the web platform through albums. It is possible to create multiple web platforms for different uses, such as for different events and brands.
Workflow
The predefined process or steps by which records are processed in the system. May include, for example, review, approval and publishing steps.