resourceIdentifier cardinality problem about mdjson-schemas HOT 9 CLOSED

I should add this applies to resourceIdentifier in citation, assignedId in extent, and resourceCitation in associatedResource.

from mdjson-schemas.

Is that not what we intended for the JSON? To allow multiple identifiers
per authority. Otherwise, you'd have to repeat the whole block.

On Fri, May 16, 2014 at 1:52 PM, stansmith907 [email protected]:

We have the cardinality reversed for resource identifier. In ISO an
identifier can have multiple authorities. Schema 0.4.0 allows multiple
identifier per authority.

Now:

{
"contactId": "",
"role": "",
"resourceIdentifier": [
{
"identifierName": "",
"identifier": ""
}
]
}

Should be:

{
"contactId": "",
"role": "",
"resourceIdentifier": {
"identifierName": "",
"identifier": ""
}
}

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9
.

from mdjson-schemas.

That is what we intended, we (me mostly) were wrong. Only one code is allowed per authority. Which makes sense when I think about it. For multiple identifiers we need to repeat the whole block anyway if one is from USGS and the other from GTPN - different authorities different contactIds.

from mdjson-schemas.

No, I meant multiple identifiers from the same authority. My assumption was
that we were not holding to the ISO limitation here. The block would need
to be repeated for ISO XML.

On Fri, May 16, 2014 at 2:09 PM, stansmith907 [email protected]:

That is what we intended, we (me mostly) were wrong. Only one code is
allowed per authority. Which makes sense when I think about it. For
multiple identifiers we need to repeat the whole block anyway if one is
from USGS and the other from GTPN - different authorities different
contactIds.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-43384813
.

from mdjson-schemas.

What would be the point? Would an authority have multiple identifier for a resource? What have I forgotten?

from mdjson-schemas.

We need input from the group to close this issue.

ISO supports multiple authorities for a single identifier. Our JSON schema supports multiple identifiers for a single authority. The question is do we really want to support the option for an authority to list (issue) multiple identifiers for the same resource? Is that reasonable? Do we know of any examples?

from mdjson-schemas.

I can't imagine the relevance of multiple identifiers issued by the same
authority for a project. There may be multiple identifiers for a long term
project as one grant ends and a new one is issued. But this seems more of
funding history and I don't know that is relevant in metadata. What the
authority's current identifier is what seems important. Allison?

On Wed, May 21, 2014 at 9:26 AM, stansmith907 [email protected]:

We need input from the group to close this issue.

ISO supports multiple authorities for a single identifier. Our JSON schema
supports multiple identifiers for a single authority. The question is do we
really want to support the option for an authority to list (issue) multiple
identifiers for the same resource? Is that reasonable? Do we know of any
examples?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-43788357
.

from mdjson-schemas.

One thing to keep in mind is that this applies to every instance of
resourceIdentifier. It's not just at the project level- it also applies
to more discrete objects, such as individual geographic features.

On Wed, May 21, 2014 at 10:19 AM, dwalt [email protected] wrote:

I can't imagine the relevance of multiple identifiers issued by the same
authority for a project. There may be multiple identifiers for a long term
project as one grant ends and a new one is issued. But this seems more of
funding history and I don't know that is relevant in metadata. What the
authority's current identifier is what seems important. Allison?

On Wed, May 21, 2014 at 9:26 AM, stansmith907 [email protected]:

We need input from the group to close this issue.

ISO supports multiple authorities for a single identifier. Our JSON
schema
supports multiple identifiers for a single authority. The question is do
we
really want to support the option for an authority to list (issue)
multiple
identifiers for the same resource? Is that reasonable? Do we know of any
examples?

—
Reply to this email directly or view it on GitHub<
https://github.com/adiwg/adiwg-json-schemas/issues/9#issuecomment-43788357>

.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-43794852
.

from mdjson-schemas.

This should be closed when #11 is resolved.

from mdjson-schemas.