DescriptiondocmappingForm

From DISMARC Help

Revision as of 07:46, 20 August 2008 (edit) Herzoga (Talk | contribs) ← Previous diff		Current revision (10:52, 11 September 2008) (edit) (undo) Admin (Talk | contribs) (Redirecting to Data Mapping)
Line 1:		Line 1:
		+	#REDIRECT [[Data Mapping]]
		+
	This form is used to submit sample data and a mapping suggestion to the [[environment.ini#MdmMails|person who is reposibile for content]] at the web site.		This form is used to submit sample data and a mapping suggestion to the [[environment.ini#MdmMails|person who is reposibile for content]] at the web site.

---

Current revision

1. REDIRECT Data Mapping

This form is used to submit sample data and a mapping suggestion to the person who is reposibile 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.

Comments keywords

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

Lookup

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.

Thesaururs

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.

$ 

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.

array('role'=>'creator')

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.

InsertNow

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 is never used

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.

Example

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

InsertNow
Lookup:dmGenre
Thesaurus:dmGenre

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.

Result

After a submission, emails will go out to the content responsible people. This mail will contain a 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.