Purpose of this story is to derive marc field 111 from the http://bibfra.me/vocab/lite/creator edge of Work resource.

Graph structure:

• A work have exactly one creator

• The creator can have multiple relations (roles) with the Work.

• Creator can have multiple identities (LCCN, VIAF, etc)

Rules for deriving Marc 111

• There should be only one occurrence of 111.

• Just in case if work has multiple creator outgoing edges (which should not happen once we have the validation rules in place), choose one of the creators. Do not mix data of multiple creators in the generated MARC 111 record.

• 111 should be derived from the resource whose type contains the value http://bibfra.me/vocab/lite/Meeting

• The mapping from Meeting resource to subfields of 111 is as given below

Special rule for deriving $0 (authority link)

$0 should combine the values from the following:

• http://bibfra.me/vocab/lite/authorityLink property of the Organization resource

• http://bibfra.me/vocab/lite/link property of all outgoing edges pointed by predicate http://library.link/vocab/map & having type http://bibfra.me/vocab/lite/Identifier

Special rule for deriving $4 (Relation code)

Identify all ‘relation’ edges, between Work and the creator. For each ‘relation’ edge, find the corresponding MARC code as described in relation_map spreadsheet

Special rule for deriving $j (Relation name)

Question: To begin with, is it enough to just use the text that comes after http://bibfra.me/vocab/relation/ in the predicate? This will be good enough for about 70% of the relations that has only one word.