Data Mapping


Jump to: navigation, search

The data mapping tool is available for special users (content coordinators).

The form is used to submit sample data and a mapping suggestion to the person who is reponsible for content at the web site.

You start off by entering your contact details. Whenever a request will be sent, the username will be sent along, just in case you forogot to enter the contact details.

Now comes the more or less technical part.

Your native data will always be transformed into an XML via a Reader. That's why the Your Field values should be a valid XPath for ONE document that was generated by the reader. In case you want CSV data to be imported, you can just write the name of the column into the Your Field fields.

Since a Mapper will be generated after you've submitted the form some processing instructions are needed most of the time.


Fieldvalue keywords

There is actually only one keyword, as the other terms will be used to search for that field in the native data

This keyword will insert the following value into the DISMARC field

Comments keywords

That's why you can add some keywords at the Your Comment fields.

By typing Lookup:<namespace> into the comments field, the mapper will automatically check the subsititutionlist for your native field with the defined namespace and will then replace the value of the field, with the looked up value. If no subsitiuion value is found, the looked up term will be used.
The same as Lookup but if no term is found in the substitution list, the search term will be left out.
This is often used combined wiht the Lookup keyword. Whenever you want an thesaurus to be used as the value of the mapped document, use this keyword with the propper thesaurus name like Thesaurus:dmEras. If the term is not found within the thesaurus, it will be used as is.
Same as Thesaurus but if the term is not found, it will be left out.
This is a modifier of the value that will be inserted. This is a good way to append or prepend values to the supported value. This is hardly used.
This keyword is used to add additional attributes to the field. hasSample has an additional title attribute as well as all the relation fields have an navigate attribute. Contributor and other fields have specific roles what will be indexed separately.
This keyword will cause the working values to be inserted at this place. The value will be inserted at the end of the processing instruction if this keyword or Thesaurus(Only) is never used
By using Append:<text> all working values will be extended using <text>. A value V with Append: hi! will result in "V hi!".
By using Prepend:<text>, <text> will be written in front of the working value. A value V with Prepend:hi will result in "hi V".
SplitAt:<string> will split the text at <string>. So a value of a/b/c with SplitAt:/ will result in three new working values a, b and c
In case you had to alter the working values to much for further use, you can use restart to use the initial values

See the comment field as processing instructions. Each value from the native fields will be written into a working value. Lookups will replace this working value.


Let's have a look at this comment field and what will happen to the value Volksmusi:


Volksmusi will be inserted right away. Then, the substitutionlist will be contacted. Folk music was returned here. With this returned value, the Thesaurus is queried. Since Volksmusi is replaced with Folk music during the Lookup, the Thesaurus will be able to return the proper Thesaurus id for the insert.


After a submission, emails will go out to the technical and content responsible people. This mail will contain an XML usable for the collection tool and a new Mapper. The Mapper has to be checked now, if the comments used the proper keywords or if other processing instructions are available.

Personal tools