ILMSinfo / RBIS: XML
From ILMS-Wiki
Contents |
General structure
The XML definition will be used to automatically create all views on the dataset (overview, detailed view, search view, edit/new view) and all SQL queries in the background. All attribute elements with given position (group and order) will be displayed except of no-matching cond-condition attributes.
Detailed description
view
- basedir: set to : ".."
- name: not in use
- title: Headline
- template (true|false): Enable function to save content as template
- parent: Parent XML-file (will be used to manipulate log entries)
Example:
<view basedir=".." name="variable" title="c_person_headline" parent="c_person_org" template="true">
rights
Controls the actions executed on the XML-file
- read (true|false): view activities
- write (true|false): write activities
- delete (true|false): delete activities
<rights read="true" write="true" delete="true"/>
id
- name: Identifier of the dataset. "md_metadata_id" should be used if available.
<id name="geodata.md_metadata_id"/>
group
map
edit
document
table
- name: table name in the database
<table name="metadata">
- cond: name of condition (if the name is not set in the config.php, the table will be ignored. The cond-attribute must be also set in the attribute and join element.)
config.php: $conditions["workgroup"] = 1;
<table name="fp_featpar_all2" cond="workgroup">
Example:
<table name="metadata"> </table>
attribute
- cond: name of condition (if the name is not set in the config.php, the attribute will be ignored. The cond-attribute can/must be also set in the table and join element.)
<attribute cond="workgroup" name="featpar" title="geo.... />
example: Primaray key
example: Selection list
example: Date
join
- cond: name of condition (if the name is not set in the config.php, the table will be ignored. The cond-attribute must be also set in the table and attribute element.)
<join cond="workgroup" from_table="geodata" ... />
