Catalog Information

Catalog entities are the top-level data structures holding the repository data and specifications. In keeping with the philosophy of CHEMCONNECT to provide as many links and additional data to repository data, some common information fields are available to supplement the information of each catalog entity.

Each catalog entity supplements their information with:

· Data Links: Data is never an independent entity and can be for example, created by, defined by, related to, derived from or used by other entities in the repository. A link is a keyword specifying what type of link is to be made this link type is chosen from the knowledge base.

· References: These are publication references, for example, with corresponding DOI number referring to the catalog entity. This could be for example, the source of the data, where the device description is found, etc.

· Web Links: Another form of referencing could be from sites on the internet with further information as to source, description, etc. of the catalog entity.

· Description (title and textual summary): There are also fields for textual description, both as a title or a longer abstract and even keywords. This information also contains the accessibility of the entity and when it was created (which may be different than when the data entry was created).

· Data concept and purpose keys: These keywords, extracted from the knowledge-base hierarchy of concept keys and purpose keys, give added context to the data. These are standardized keywords which give added information about the nature of the data and also gives context of the data in relation to other data that lie in the same place in the concept tree.

· Owner and Visibility: The owner of the data is the researcher that originally entered the data. It is the owner who determines the visibility and editability (including removal) of the data for other users. The visibility can be just the owner, a consortium of users or even public.

· Place in catalog hierarchy: The place in the catalog hierarchy has three entries:

o The base position in the hierarchy. The corresponds to a directory structure of data objects.

o The second field indicates what type of data the object represents. This data key is determined/selected from the knowledge base.

o The simple name of the data object (that is unique for the position within the hierarchy).