EnterWorks can be configured to have multiple repositories. Each repository is designed to hold only one kind of data. For example, a repository might hold information about a company's products or the contact information for all their customers, but not both.
The data is stored in records. Each record contains data that pertains to a particular item, such as a product or a customer.
Every record in a repository has the same format or structure, which is defined by the repository's profile.
A repository's profile determines which attributes (data items) the repository will store for each record, the data type of each attribute, and the order the attributes are stored in the record. Each record in the repository has the same list of attributes, but since not all attributes pertain to all records, a record may have unused (or empty) attribute values.
For example, suppose a business that sells movies has a repository for storing information about the movies they sell. The repository would have a record for each movie. The repository's profile would determine what information was stored for each movie -- the movie's attributes, for example: the title of the movie; availability date; rating; director; and cast. Some of a record's attributes may be empty, for example, if the availability date of a movie was unknown.
EnterWorks supports several types of repositories, which differ in the way they are used and the actions allowed to be performed on them. While some of these uses and actions are pre-defined by EnterWorks, some are also configurable.
A Repository View is a display of the records in a repository.