Handling' Additional Documentation' as 'Aggregate Information' about mdjson-schemas HOT 3 CLOSED

Good catch. I'd probably vote that we don't bother with association type
until -1, when it'll just be a CI_Citation class referenced from the
MD_Identification block. Do we have any idea when we'd be able to start on
the -1 version of the writer? If that will be a long, long time then it
might be better to add the association type code in the meanwhile.

On Fri, Sep 12, 2014 at 4:35 PM, stansmith907 [email protected]
wrote:

In our last Tuesday meeting, Chris suggested we carry
'additionalDocumentation' as gmd:MD_AggregateInformation'. Sounded like a
great idea, but has a few hickups.

• Besides citation, aggregateInformation requires 2 additional
  parameters not supplied in our JSON; 'association type' and 'initiative
  type'.
  • Association type is required and there is currently no suitable
    value in this codelist we could use, it would need to be extended.
    'Inititative type also has no suitable values but is not required - so not
    a problem.

The best way to do this might be to ...

• extend the association type codelist to support a new code
  (inserting 'other' or 'supporting') rather than modify the adiwgJson -
  which would not be clean for 19115-1;
• have the 19115-2 additionalDocumentation writer automatically insert
  the missing association type.

Options:
[ ] add association type code
[ ] don't bother with additional documentation in 19115-2

—
Reply to this email directly or view it on GitHub
#20.

Chris Turner
Data Librarian | Axiom Consulting & Design
[email protected]

from mdjson-schemas.

We can start -1 as soon as NOAA publishes the XSD which is suppose to be
late this year or early next.

Stan Smith
Sent from mobile
907.223.8752
On Sep 12, 2014 5:35 PM, "chris turner" [email protected] wrote:

Good catch. I'd probably vote that we don't bother with association type
until -1, when it'll just be a CI_Citation class referenced from the
MD_Identification block. Do we have any idea when we'd be able to start on
the -1 version of the writer? If that will be a long, long time then it
might be better to add the association type code in the meanwhile.

On Fri, Sep 12, 2014 at 4:35 PM, stansmith907 [email protected]
wrote:

In our last Tuesday meeting, Chris suggested we carry
'additionalDocumentation' as gmd:MD_AggregateInformation'. Sounded like
a
great idea, but has a few hickups.

• Besides citation, aggregateInformation requires 2 additional
  parameters not supplied in our JSON; 'association type' and 'initiative
  type'.
• Association type is required and there is currently no suitable
  value in this codelist we could use, it would need to be extended.
  'Inititative type also has no suitable values but is not required - so
  not
  a problem.

The best way to do this might be to ...

• extend the association type codelist to support a new code
  (inserting 'other' or 'supporting') rather than modify the adiwgJson -
  which would not be clean for 19115-1;
• have the 19115-2 additionalDocumentation writer automatically insert
  the missing association type.

Options:
[ ] add association type code
[ ] don't bother with additional documentation in 19115-2

—
Reply to this email directly or view it on GitHub
#20.

Chris Turner
Data Librarian | Axiom Consulting & Design
[email protected]

—
Reply to this email directly or view it on GitHub
#20 (comment)
.

from mdjson-schemas.

Okay, will not support additional documentation in 19115-2.

from mdjson-schemas.