Re: How to store external article identifier?

Yes Alasdair is right, there are several ways you could reference an
external identifier if it has a network addressable value.  For example:

   - "identifier": "http://viaf.org/viaf/96994048",

   - "identifier": [
        {
         "@type": "PropertyValue",
          "propertyID": "http://viaf.org",
          "value":  "96994048",
          },
   - "identifier": [
        {
         "@type": "PropertyValue",
          "propertyID": "VIAF",
          "value":  "96994048",
          "sameAs":  "http://viaf.org/viaf/96994048",
          },

... and permutations thereof.

~Richard.

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw



On Tue, 16 Jul 2019 at 15:31, Gray, Alasdair J G <A.J.G.Gray@hw.ac.uk>
wrote:

> Hi
>
> Another solution which gives a distinction between the identifiers is to
> use the identifed property for the identifier that you assign and the
> sameAs property for all the external identifiers.
>
> Alasdair
>
> http://www.macs.hw.ac.uk/~ajg33
>
> ------------------------------
> *From:* Richard Wallis <richard.wallis@dataliberate.com>
> *Sent:* Tuesday, July 16, 2019 9:51:35 AM
> *To:* Abir Hossain
> *Cc:* public-schemaorg@w3.org; Jeremy Kelaher
> *Subject:* Re: How to store external article identifier?
>
> Hi Abir,
>
> All properties in Schema.org are repeatable so the simple answer to your
> question is yes.
>
> If you are storing multiple identifier values, it would make sense to
> capture which identifier is which,   If you have not done this before,
> checkout the examples that use a PropertyValue type to capture the
> identifier (value) and its type (propertyId) - like this:
>
>
>    1.
>    2. "identifier": [
>         {
>          "@type": "PropertyValue",
>           "propertyID": "Internal Id",
>           "value":  "889647468"
>           },
>         {
>            "@type": "PropertyValue",
>            "propertyID": "External id",
>            "value":  "AB23C"
>         }
>      ],
>    3.
>
> Richard Wallis
> Founder, Data Liberate
> http://dataliberate.com
> Linkedin: http://www.linkedin.com/in/richardwallis
> Twitter: @rjw
>
>
>
> On Tue, 16 Jul 2019 at 08:28, Abir Hossain <Abir.Hossain@sbs.com.au>
> wrote:
>
>> Hi,
>>
>>
>>
>> I’m wondering if someone can help me with schema question regarding
>> articles. How can we store multiple identifiers for an article? I work in a
>> media organisation where we have articles coming from various sources, and
>> once they get ingested they are assigned an internal identifier, but we
>> want to be able to save their external ids as well. Can the identifier
>> field within a Thing be a list of multiple values?
>>
>>
>>
>> Regards
>>
>> Abir
>>
> ------------------------------
>
> *Heriot-Watt University is The Times & The Sunday Times International
> University of the Year 2018*
>
> Founded in 1821, Heriot-Watt is a leader in ideas and solutions. With
> campuses and students across the entire globe we span the world, delivering
> innovation and educational excellence in business, engineering, design and
> the physical, social and life sciences. This email is generated from the
> Heriot-Watt University Group, which includes:
>
>    1. Heriot-Watt University, a Scottish charity registered under number
>    SC000278
>    2. Edinburgh Business School a Charity Registered in Scotland,
>    SC026900. Edinburgh Business School is a company limited by guarantee,
>    registered in Scotland with registered number SC173556 and registered
>    office at Heriot-Watt University Finance Office, Riccarton, Currie,
>    Midlothian, EH14 4AS
>    3. Heriot- Watt Services Limited (Oriam), Scotland's national
>    performance centre for sport. Heriot-Watt Services Limited is a private
>    limited company registered is Scotland with registered number SC271030 and
>    registered office at Research & Enterprise Services Heriot-Watt University,
>    Riccarton, Edinburgh, EH14 4AS.
>
> The contents (including any attachments) are confidential. If you are not
> the intended recipient of this e-mail, any disclosure, copying,
> distribution or use of its contents is strictly prohibited, and you should
> please notify the sender immediately and then delete it (including any
> attachments) from your system.
>

Received on Tuesday, 16 July 2019 14:49:44 UTC