Comments (notes, instructions and so on) that can be attached to specific XML elements within an entry. |
|||||
A number of entries grouped together to form a chunk of work. Batches are created and allocated to editors with due dates, in order to manage the flow of work. See also Group, Tasks, Tags. |
|||||
An element that forms part or all of the current element's content. An element may have any number of children. See also Entry Editor. Related topics: Entry Editor, Entry Editor Shortcuts). |
|||||
The element that is highlighted, or that which contains the cursor. See also Entry Editor. Related topics: Entry Editor, Entry Editor Shortcuts). |
|||||
The hierarchical structure of your data, as visually displayed in the Tree View. |
|||||
An element that is the current element's child, the child of a child, etc. See also Entry Editor. Related topics: Entry Editor, Entry Editor Shortcuts). |
|||||
An entry that has been deleted from a project. Note that its data will still be stored in the repository so discarded entries may be re-instated by the Project Manager or System Administrator. |
|||||
'Document Type Definition' is a file that contains a set of editorial and design rules to be applied to specific projects. A separate DTD is configured for each individual project. |
|||||
Term used to acknowledge that the editorial work done on a project is in keeping with the rules set up in the project's DTD. |
|||||
An XML element and its content, both text and other elements. (see also Entry Editor in glossary) (related topics: Entry Editor, Entry Editor Shortcuts) |
|||||
A small program that comes as part of the DPS Software package. It is downloaded to each individual User's local computer and is the main component used for editorial and lexicographical work. |
|||||
Usually the headword, configured by the System Administrator. The entry label is a project-specific text string that identifies individual entries, distinguishing between entries that share the same headword; common formulae are headword plus homograph number or headword plus part of speech. |
|||||
The sibling that is located immediately after the current element. See also Entry Editor. Related topics: Entry Editor, Entry Editor Shortcuts). |
|||||
A way of grouping together entries so they can be easier searched for, and retrieved. |
|||||
The main name or 'heading' for an entry. For example, in a dictionary, the headword is the word you would look up: abort, about, abridge and so on. |
|||||
A specific place where new content is able to be inserted, as determined by the DTD. |
|||||
A small file that allows you to download the DPS Entry Editor software and install it on to your own computer. This file is supplied by IDM. |
|||||
Specific keystrokes that allow Users to use shortcuts. For example, instead of choosing File |
|||||
To open a program, screen or specific DPS function. For example, 'click the icon to launch the template picker'. |
|||||
Entries that have been downloaded by a user and are thus locked to anyone else. This is an automatic process that forms part of the DPS's version control and it prevents duplication of work. |
|||||
Metadata is information associated with an entry, but not part of the entry. This might include Tags or Annotations that have been added to an entry. Metadata will only appear in the mechanics of the DPS System and will not appear in published versions of your data. |
|||||
A peripheral part of the Repository where entries are stored before they are approved. Once approved they will leave the Outstore and go into the main Repository. |
|||||
The element of which the current element is a child. An element must have exactly one parent.(see also Entry Editor in glossary) (related topics: Entry Editor, Entry Editor Shortcuts) |
|||||
A string of words or symbols used to search the database. Also known as "Syntax". |
|||||
The sibling that is located immediately before the current element. (see also Entry Editor in glossary) (related topics: Entry Editor, Entry Editor Shortcuts) |
|||||
A specific book or dictionary project that is being developed using the DPS. The DPS is specially configured for each individual project. |
|||||
The specific set-up of the system to suit a particular project. For example, the permissions allowed for each User. |
|||||
Within the DPS System 'Process' refers to an action that is required to complete a project. Some examples of processes include: Content Update, Edit, Proofread. the Project Manager will determine the necessary Processes at the beginning of a project. |
|||||
A means of editing an entry through the DPS Website. |
|||||
A range of entries, for example 'a to abe'. |
|||||
The data store on a DPS Website, with which the Entry Editor can communicate to retrieve entries for editing, and then upload the revised versions. |
|||||
An element that shares the same parent as the current element. An element can have any number of siblings and data can also be input as a preceding sibling or a following sibling. (See also Entry Editor, Data Structure) (related topics: Entry Editor, Entry Editor Shortcuts) |
|||||
Used to describe the progress of each individual entry, for example an entry status could be 'uploaded', 'submitted' or 'approved'. |
|||||
A DPS step is a subdivision of a process. A process's steps must be performed in a defined order. Steps may be compulsory or optional, but a process must have at least one compulsory step. For a process to be completed, all its compulsory steps must be performed in the proper order. |
|||||
A means of creating a group of entries that can be searched for by their Tag. This method groups specific versions of entries so if one of those entries is updated the Tag will still display the older version. |
|||||
The application of a Process to a manageable unit of work. For example, if the Process is to proofread a whole dictionary (thousands of entries!) the Project Manager might create a number of Tasks such as proofreading letter A, proofreading letter B and so on, so the overall Process can be undertaken in a realistic manner. |
|||||
The text that is the content of an element. Textual content may itself contain elements.(see also Entry Editor in glossary) (related topics: Entry Editor, Entry Editor Shortcuts) |
|||||
Entries that are not currently downloaded by another user (i.e. noone else is working on them) allowing them to be downloaded and worked on by anyone with the correct permissions. |
|||||
A means of ensuring the DTD and editorial guidelines are being adhered to. Editorial work must conform to certain rules (determined by the Publisher at the beginning of a project) and if those rules are broken the entry will be flagged as invalid. |
|||||
Within this documentation "Website" refers specifically to the DPS Website. Related Topics: The DPS Website. |
|||||
There are two types of "Workflow" referred to in this documentation:
|