Ticket #689 (closed metadata: wontfix)

Opened 12 years ago

Last modified 12 years ago

[M] [WG] BADC metadata content shows up problem with online references

Reported by: lawrence Owned by: lawrence
Priority: discussion Milestone: Reporting
Component: community Version:
Keywords: Cc:

Description

Suspect Kev knows all about this, but

badc.nerc.ac.uk__NDG-B1__dataent_chablis

has

<dgMetadataDescription>
      <descriptionSection>
            <descriptionOnlineReference>
                <dgSimpleLink>
                    <name>URI</name>
                    <URI>http://badc.nerc.ac.uk/data/chablis</URI>
                </dgSimpleLink>
            </descriptionOnlineReference>
        </descriptionSection>
        <descriptionSection>
            <descriptionOnlineReference>
                <dgSimpleLink>
                    <name>Logo</name>
                    <URI>http://badc.nerc.ac.uk/graphics/logos/nerc-2.gif</URI>
                </dgSimpleLink>
            </descriptionOnlineReference>
      </descriptionSection>
</dgMetadataDescription>

What's the point of the name as used here? As a consumer of these records I can't use them, either it should be a controlled vocabulary or it should be something I can use as the text content of an <a> entity.

Change History

comment:1 Changed 12 years ago by selatham

  • Owner changed from selatham to lawrence

I put a name in the descriptionOnlineReference/dgSimpleLink as it's mandatory.

These names come from the moles catalogue - probably as a the name field was originally a restricted vocab. Now that there is a specific 'Logo' group,  moles:logo/LogoURI, I populate this group specifically with descriptions with name = 'Logo' in the catalogue. But I put the logo URI in as a general description too for good measure.

If we should have something else here then it needs to be specified.

comment:2 Changed 12 years ago by lawrence

  • Owner changed from lawrence to selatham

A simple link is an html <a href="URI">NAME</A>. The usage in the backend catalogue needs to reflect this!

comment:3 Changed 12 years ago by selatham

  • Owner changed from selatham to lawrence
  • Milestone changed from BETA to PROD Step2

I'm not sure what you're asking for in the Moles. There's now a dgReferenceClass which uses a standard vocab to describe what this online reference is about. See example below.

−
	<descriptionOnlineReference>
−
	<dgSimpleLink>
<name>URI</name>
<URI>http://badc.nerc.ac.uk/data/chablis</URI>
</dgSimpleLink>
−
	<dgReferenceClass>
<dgValidTerm>DataPage</dgValidTerm>
−
	<dgValidTermID>
<ParentListID>http://vocab.ndg.nerc.ac.uk/term/N041</ParentListID>
<TermID>3</TermID>
</dgValidTermID>
</dgReferenceClass>
</descriptionOnlineReference>

comment:4 Changed 12 years ago by lawrence

I didn't know about the reference class, thanks ... but

My point still remains; a dgSimpleLink should have the same semantics as an html hyperlink, that is, you should populate the NAME variable with something that the consumer might use to build a hyperlink ... it's completely spurious putting URI in the name ... I know it's a uri, the next element tells me it is.

comment:5 Changed 12 years ago by lawrence

  • Owner changed from lawrence to selatham

comment:6 Changed 12 years ago by selatham

  • Owner changed from selatham to lawrence

So these names are a bit redundant now that there is a dgReferenceClass. Is this actually a problem for NDG2? If not put back to Reporting and Futures as an issue on TI07-Moles.

comment:7 Changed 12 years ago by selatham

  • Milestone changed from PROD Step2 to Reporting and Futures

comment:8 Changed 12 years ago by selatham

  • Status changed from new to closed
  • Resolution set to wontfix

We are using links OK. Future of moles.

Note: See TracTickets for help on using tickets.