Skip to content

Commit

Permalink
Update crewMemberCollection.md (#34)
Browse files Browse the repository at this point in the history
  • Loading branch information
ehennestad authored Nov 15, 2024
1 parent 988e758 commit f523d97
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/tutorials/crewMemberCollection.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,13 @@ Let us create a set of metadata instances from this table that represents the cr

With these assumptions we will create:

- a metadata <samp>Collection</samp> for storing metadata instances
- a unique set of <samp>Consortium</samp> instances based on the name given in the <samp>memberOf</samp> column
- a <samp>ContactInformation</samp> instance based on the <samp>email</samp> column
- a <samp>Person</samp> instance for each table row with:
- the <samp>givenName</samp>, <samp>familyName</samp>, and <samp>alternateName</samp> (if available)
- a link to the respective <samp>ContactInformation</samp> instance
- a person-specific embedded <samp>Affiliation</samp> instance that links to the respective <samp>Consortium</samp> instance
- a metadata <samp>Collection</samp> for storing metadata instances
- a unique set of <samp>Consortium</samp> instances based on the name given in the <samp>memberOf</samp> column
- a <samp>ContactInformation</samp> instance based on the <samp>email</samp> column
- a <samp>Person</samp> instance for each table row with:
- the <samp>givenName</samp>, <samp>familyName</samp>, and <samp>alternateName</samp> (if available)
- a link to the respective <samp>ContactInformation</samp> instance
- a person-specific embedded <samp>Affiliation</samp> instance that links to the respective <samp>Consortium</samp> instance

We start by creating an empty metadata collection for storing metadata instances.

Expand Down

0 comments on commit f523d97

Please sign in to comment.