align ISNI properties with VIVO-ISF

[mellybelly]

we should review the ISNI properties between organizations and types of organizations and try to reconcile these.

Does anyone know where we can find these and/or have a contact?

[mconlon17]

Ringgold.comhttp://Ringgold.com might be useful. Search for isni and see the properties. Don't know if there is an API or definitions for properties.

Mike

On Aug 13, 2015, at 12:16 PM, Melissa Haendel <notifications@github.commailto:notifications@github.com> wrote:

we should review the ISNI properties between organizations and types of organizations and try to reconcile these.

Does anyone know where we can find these and/or have a contact?

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

[mellybelly]

Also see http://www.isni.org/content/documents-related-data-submission

[arademaker]

The quality of the data returned from the search interface http://www.isni.org/search is really bad. The properties/values presented in the results of the search are also nothing more that we have already in FOAF. I really don't see much value on this issue. What do you think ISNI can add to VIVO-ISF? But maybe I am missing something here...

[mellybelly]

I think there is a better organizations file available from Digital Science, lets take a look at that?

[mconlon17]

Agree — I saw the rollout presentation of their new service/data called GRID — global research identification data. Freely available with licenses for reuse for download as a single file. Available “September.” Looks quite good. 45,000 higher ed institutions around the world. With ISNI, a GRID identifier, and a URI. Has lat and long, official name, and some affiliation/part information. They expect the data will improve (and remain free open linked data) in the future.

Mike

On Aug 18, 2015, at 6:38 AM, Melissa Haendel <notifications@github.commailto:notifications@github.com> wrote:

I think there is a better organizations file available from Digital Science, lets take a look at that?

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