Stephen,
This is an interesting example of using shared identifiers and then
pooling the results. As and when the identifiers are persistent Linked
Data ones, that will be even better. Using a standard resource like the
OS Open Data gives you the added benefit of geolocation for your
records, but care needs to be taken over licensing terms and intended
use of the data. Also, for some collections the lack of an historical
perspective may be an issue; as may the scope (U.K. only) for others.
Do other list members have experiences of using geo authorities to
share? I've experimented with both Geonames [1] and OSM [2]; neither is
ideal. At the Pelagios Linked Pasts workshop earlier this week,
Wikidata [3] was being suggested as a potential solution. Then of
course there is now the TGN [4]. All offer some sort of API, so we
could potentially set up 'widgets' to support capture of their URLs
rather than needing to download the whole resource and set up a local
termlist.
Richard
[1] http://www.geonames.org/
[2] http://www.openstreetmap.org/
[3] https://www.wikidata.org/
[4] http://vocab.getty.edu/tgn/
On 24/07/2015 13:07, Stephen McConnachie wrote:
> Hi everyone,
>
> I thought this might be of interest on a rainy Friday: a blog I wrote for the Ordnance Survey about the BFI's use of their Open Data product to create the data spine which underpins our mass digitisation and map visualisation project, Britain on Film.
>
> OS blog:
> http://www.ordnancesurvey.co.uk/blog/2015/07/mapping-britain-on-film-with-os-opendata/#more-19804
>
> Britain on Film:
> http://player.bfi.org.uk/britain-on-film/
>
> I've always intended to share the UK Location hierarchy (once I've improved it in reference to the next generation of OS open data, which has persistent unique identifiers) with fellow Adlib users who are interested, as it is importable to any Adlib thesaurus very easily (and the OS open data licence lets me share it as long as recipients agree to the same terms).
>
> I can also consider sharing it beyond the Adlib community if there's any interest, as it's exportable in a very transparent XML markup which could inform a simple import to any system I suspect.
>
> Stephen
>
> ****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
> ****************************************************************
>
--
*Richard Light*
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|