search

adiwg / mdTranslator

Metadata translation tool built using Ruby
https://www.adiwg.org/mdTranslator/
The Unlicense
14 stars 12 forks source link

FGDC writer for voucher requires repository #174

Closed stansmith907 closed 6 years ago

stansmith907 commented 6 years ago

In mdJson the voucher repository is a responsibility object (responsible party). Responsibility requires a role and at least one party which is a contactId. Since party is an array and FGDC can output only one contact the first contact is taken, others are ignored. The FGDC reader automatically sets the repository role to 'curator'. The mdJson reader sets it to whatever was specified in the mdJson record.

The problem is that the FGDC writer is searching the responsibility object for a specific role type of 'custodian', which it may not be, in which case the repository output is skipped and an error message generated.

Two problems here:

  1. We need to decide what the role type of the specimen guardian should be. 'curator', 'custodian', '?'
  2. There is actually no need to check the role type when processing the repository responsibility object since repository is not an array and only one role type is allowed per responsibility object. Also, because the repository responsibility object is already placed in proper context any role should be acceptable.
dwalt commented 6 years ago

Just to clarify, voucher is an array in FGDC. However, as Stan pointed out, only one citation is provided for per voucher reference. Often the citation is an organization that is owner/custodian of the collection repository. The person is usually offered as a contact point, if there is one. If you want to use one role for both, then "custodian" may be best.

On Thu, Jan 18, 2018 at 4:31 PM, stansmith907 notifications@github.com wrote:

In mdJson the voucher repository is a responsibility object (responsible party). Responsibility requires a role and at least one party which is a contactId. Since party is an array and FGDC can output only one contact the first contact is taken, others are ignored. The FGDC reader automatically sets the repository role to 'curator'. The mdJson reader sets it to whatever was specified in the mdJson record.

The problem is that the FGDC writer is searching the responsibility object for a specific role type of 'custodian', which it may not be, in which case the repository output is skipped and an error message generated.

Two problems here:

  1. We need to decide what the role type of the specimen guardian should be. 'curator', 'custodian', '?'
  2. There is actually no need to check the role type when processing the repository responsibility object since repository is not an array and only one role type is allowed per responsibility object. Also, because the respiratory responsibility object is already placed in proper context any role should be acceptable.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/adiwg/mdTranslator/issues/174, or mute the thread https://github.com/notifications/unsubscribe-auth/AF6hL5PtZCGHAsVLCwQ1hGmlKVppv6s2ks5tL_BygaJpZM4Rj2-0 .

stansmith907 commented 6 years ago

To clarify just a bit more, in mdJson and ISO voucher repository is a 'responsibility` (new term for responsible party); in FGDC it is a 'contact'. Citation is not part of voucher. And contact can be either person or organization, no problem there.

'Custodian' is good for me.