Tools & Users - Meta Data Editor.

Getting started.

The Meta Data Editor allows you to add meta data to forms. In the directory \project35-1.0-win, click on run_meta_data_editor. A pop up dialog will appear like the one shown on the right. Select the model you've used to create data entry forms.

The parts of the screen.

The picture on the right shows an example screen shot of the Meta Data Editor. Although most of the screen will look the same for all models, some features will depend on concepts defined in the model you have selected.

Along the top is the menu bar. On the left is the navigation tree. Clicking on any of the entries in the tree will take you to that particular form. On the right is the current form you are filling out.

This section will divided into groups based on the type of information being explained. These groups are: Menus, Buttons, Forms & Fields.

Menus

There are a variety of menu options with the Meta Data Editor.

Menu List	What you can select and what happens
	Favourites - shows a list of the models you have used most often in the current session; Open Meta Data... - opens the .META file contained within a selected .PDZ file; Save Meta Data... - saves the .META file contained within a selected .PDZ file; Close - closes the current .META file; Exit - exits the programme. You will prompted to save any unsaved changes.
	Copy - Used to select text or parts of the navigation tree in the currently edited document; Paste - Used to paste text or parts of the navigation tree of some document into the currently edited one; Search and Replace... - a dialog prompts you for the term you wish to find and the term you wish to replace it with; Insert Symbols... - a dialog provides a list of symbols that you can select to insert into a field.
	Font - allows you to change the size of the font; Show Errors - a dialog appears that indicates where in your set for forms you have errors; Show Dependencies... - a dialog appears that indicates were there are fields that depend on other fields.In the current release of Project35, you will not need to use this feature in the Meta Data Editor; Show Changes - Colours some symbols in the navigation tree blue to indicate records that have been altered since the last time you saved your changes to the current document ; Search... - a dialog appears to help you search for terms. There is both a simple and advanced search; Clear - Removes any special highlighting in the document as a result of using other View features.
	Describe this document... - a dialog lets you include information about the document eg: title, author, e-mail, institution, and description; Alerts... - a dialog lets you to associate existing alerts bundles to the current set of forms. In the current release of Project35, you will not need to use this feature in the Meta Data Editor;
	This provides a list of the various windows, or set of forms, you may have open. Selecting something from the list will take you to that model.
	About... - provides information about Project35; Schema information... - provides information about the current schema; Enable context help - Allows you to mouse over fields and for those that have additional information, view this by clicking.

Buttons.

Throughout the various forms, you will see a variety of buttons. Some will occur on every form; others will only occur for specific kinds of fields. Below is a table that can be used for reference if you encounter a button you have not seen before and don't know what it does.

Button	What happens when you click it
	This allows you to add more terms to the given field.
	This opens a file selection dialog. Once you choose a file, the name of it will appear in the field.
	This allows you move back to the form just above the one you are on without saving any of the changes you have made since the last time you saved the form. This button occurs on all forms
	This button can occur at either the form or the field level. At the form level, this allows you to remove the particular form you are working on and does not save any information. At the field level, you would select an item from a list and this allows you to remove the selected item.
	This allows you to save changes made on a particular form and automatically move to the form up a level from where you are. This button occurs on all forms.
	This allows you to make changes to an existing item in a field where the entries lead to subforms.
	This allows you to save changes made on a particular form but keeps you on the form. This button occurs on all forms.
	This allows you to reorder entries in the tree on the left hand side of the screen. This will only move a selected entry down and only within other entries on the same level of the tree.
	This allows you to reorder entries in the tree on the left hand side of the screen. This will only move a selected entry up and only within other entries on the same level of the tree.
	This allows you to make entries in a field for the first time and have that become the current form.
	This allows you to launch extensions.

Forms & Fields

In order to minimise the number of web pages you have to look at and we have to maintain, we have decided not to include screen shots of every single field that appears in the Meta Data Editor. However, we do want to ensure that each feature in the Meta Data Editor is adequately explained. We have come up with a compromise solution for this help page which balances coverage and brevity. Don't worry if you can't make out all the text on the images. They are reduced screen shots of the actual forms. Even if we had the larger versions of the images, we still wouldn't be able to get a single screen shots of many forms because of their length or height. Fields in bold are required. Fields with a * in front of them mean that they are related to a list of terms that could come either from the list of elements in the schema or from a linked onotology.

The following list is set out with each form being shown with a list of any other forms that either link to it or are linked from it. These listings are only meant to show the immediate forms above or below the current one and not the entire hierarchy of forms in the Meta Data Editor. If a form has no forms above it in the schema, then there will be nothing before it. If a form has no other forms that come after it, then there will be nothing after it. Below this is a list of the fields that can be found on the current form and what is meant to go in them.

When we were first developing the Meta Data Editor, we weren't sure what kind of information should be recorded about ontology terms that are used to mark-up form fields. We decided to include fields that are specified in the SKOS Core Vocabulary Specification, W3C Working Draft 2, November 2005. It is a working draft of a standard being developed by the Semantic Web Best Practices and Deployment Working Group.

Although you can edit most of these fields, we expect that values for them will be supplied by ontology services. We believe you'll spend most of your time adding or changing ontology terms that have been used to describe your documents.

Form: PROJECT35_META_DATA	Links to the following forms
	--> RECORD_META_DATA

Fields	What is meant to go in them

title	This is the title of the data set.
author	This is the author of the data set.
email	The e-mail of the author of the data set.
institution	This is the institution/organisation of the author who created the data set.
description	This is describes the nature of the data set.
record_meta_data	A collection of record forms that retain information about record types that appear in the document.

Forms that link to this one	Form: RECORD_META_DATA	Links to the following forms
PROJECT35_META_DATA -->		FIELD_META_DATA -->

Fields	What is meant to go in them

name	The name of the record type.
frequency	The number of times the record type appears in the document.
field_meta_data	Meta data held about edit fields.

Forms that link to this one	Form: FIELD_META_DATA	Links to the following forms
RECORD_META_DATA -->		--> ONTOLOGY_TERM

Fields	What is meant to go in them

*name	The name of an edit field defined in the target schema.
ontology_term	A collection of ontology term instances that record meta data about terms used to mark-up form fields.

Forms that link to this one	Form: ONTOLOGY_TERM	Links to the following forms
FIELD_META_DATA -->		--> SUPER_CLASS
		--> SUPER_PROPERTY
		--> DOMAIN
		--> RANGE
		--> CHARACTERISTIC
		--> INVERSE_OF
		--> REPLACES
		--> REPLACED_BY

Fields	What is meant to go in them

ontology_service_code	A code that uniquely identifies the ontology service that was used to mark up the form field.
ontology_service_name	Name of the ontology service.
ontology_service_author	Name of the person who created the service.
ontology_service_description	Description of what the ontology service does.
ontology_service_version	Version of the software used to make the ontology service.
ontology_service_formalism	What are the ways of expressing an ontology.
ontology_service_email	The e-mail of a contact person associated with the development of the ontology service.
type	Choose if the term is a class or a property.
identifier	A unique identifier for an ontology term. Unlike the "label", the identifier will be designed to be read my machines, not people.
label	A human-readable label.
definition	An explanation of the meaning of a class or property.
comment	Additional information about meaning and/or proper use.
example	An example of the use of a class or property.
status	The status (stability level) of the class or property.
version_information	Information about the modification and/or history of a class or property.
image	The name of an image file that represents the term.
issued(dd/MM/yyyy)	Date on which the class or property was issued.
modified(dd/MM/yyyy)	Date on which the class or property was last modified.
depricated(dd/MM/yyyy)	Date on which the class or property was depricated.
super_class	Any declared super-classes (classes only).
super_property	Any declared super-properties (properties only).
domain	The declared domain for the property (properties only).
range	The declared range for the property (properties only).
characteristic	Any declared logical characteristics for the property (properties only).
inverse_of	(Properties only) Any declared inverse properties (properties only).
replaces	Any deprecated terms that the given term has replaced in recommended usage.
replaced_by	The term to use instead of the deprecated term (deprecated terms only).

Forms that link to this one	Form: SUPER_CLASS
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for super class.

Forms that link to this one	Form: SUPER_PROPERTY
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for super property.

Forms that link to this one	Form: DOMAIN
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for domain.

Forms that link to this one	Form: RANGE
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for range.

Forms that link to this one	Form: CHARACTERISTIC
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for characteristic.

Forms that link to this one	Form: INVERSE_OF
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for inverse of.

Forms that link to this one	Form: REPLACES
ONTOLOGY_TERM -->

Fields	What is meant to go in them

identifier	A unique identifier for replaces.

Forms that link to this one	Form: REPLACED_BY
ONTOLOGY_TERM -->