Skip to end of metadata
Go to start of metadata

Page Contents

View or Edit

If a Corpus is associated with some governance area, every user with any governance role in this are will be able to, at least, view it. For any other user to view or edit assets contained in a Corpus, a manager must use the Corpus's utilities > User Roles settings (see documentation) to grant them permissions.

Note that different workflows that process changes to a Corpus can have their own role-permission settings (for background, see Workflow Overview: Asset Collection Permissions: ...).


Edits made directly in an asset collection are visible to all other collections that include it and to any workflows. In contrast, edits made as part of a workflow are only visible within the working copy managed by the workflow until and unless workflow changes are committed.

To edit (or view) a Corpus, navigate to either a production or workflow copy and select the Edit (or View) link adjacent to its name.

Corpora Editor

To view or edit a production or workflow copy of a Corpus, click the view/edit link adjacent to its name in its utilities view (e.g., production, workflow). The following screen shot shows EVN Corpora editor with a Corpus named "MyCorpus 123":

The elements listed below describe the editor user interface:

  1. The list of Document instances, or instances of whichever class and subclasses of the one selected as so in Settings > Document Class.
  2. Basic metadata properties for the selected Document, 
  3. Actual contents for the selected imported Document. Depending on its source format, it can be raw plain text, whole rendered HTML pages or selected HTML nodes when Settings > CSS Selectors were configured, or raw text parsed from other formats such as PDF.
  4. Other metadata properties that depend on those parsed from the data source by Tika and could not be assigned human-readable labels. The variety of these properties is not specific to Documents' format but to each and every Document instance, i.e. this means that Documents pairs that look similar may have very different sets of metadata properties.

The editor is a real-time view of the Corpus and will show all retrieved Documents at the moment its main screen is loaded, which can happen at the same time as Manage > Refresh All Documents or Check for Updates actions run (for connected corpora).

While most other assets collections editors allow modifying their browsed assets, the Corpora editor is read-only and does not permit creating or modifying Documents after they are imported from a data source.

 

  • No labels