| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Want to organize your cloud files? Sign up for a free webinar to see how Dokkio (a new product from PBworks) can help you find, organize, and collaborate on your Drive, Gmail, Dropbox, and Slack files: Weds, May 27 at 2PM Eastern / 11AM Pacific
View
 

blank open cultural data project case study

Page history last edited by Mia 7 years, 7 months ago Saved with comment

Cultural data is data about objects, publications (books, pamphlets, posters, musical scores, etc), archival documents, etc created and distributed by museums, libraries, archives and other organisations.  These case studies can include open cultural data projects such as image sets, because full Linked Open Data is sometimes difficult for cultural heritage organisations.  ‘Open cultural data’ is data from cultural institutions that is made available for use in a machine-readable format under an open licence. 

 

Screenshots

(e.g. a sample collections page, a query results page, documentation page, or even better - something made with the open cultural data)

 

Contacts

(where can people find out more?)

 

Project URLs

Follow their progress at: (blog, twitter etc)

Machine-readable data link: (link to the endpoint, API, etc)

Documentation: (hopefully including technical documentation, code examples, term lists and explanations of the data models) 

License:

Data usage guidelines:

Sandpit: (is there somewhere you can test out queries?)

Press release: (or announcement blog post, etc)

 

What's available?

What kind of collections? (Probably quite closely related to what the organisation collects!)

How many?

Includes metadata? (who, what, where, when, material, size, location - the basics)

Includes data? (The full collections record including descriptions, interpretive themes, narratives, etc)

Includes digital surrogates? (e.g. images of the object, transcribed text of book or document, 3D printer files, etc)

(List licenses if different from default)

 

Data interface type(s) and format(s)

(e.g. SPARQL endpoint; REST API as RDF/XML; Notation-3; Tutle; JSON)

 

Ontologies, vocabularies

 

Licence(s)

 

Project summary

Date started:

Date launched:

Reason/motivation:

Partners/funders/provocateurs, etc:

Linked from relevant main site sections? (i.e. can you find mention of it on the site that most people would see?)

Designed for use internally? (are they drinking their own champagne and building a service they will use for internal or partnership projects?)

Future plans?

 

Reception, comments, projects that have used the data...

 

Comments (1)

Mia said

at 7:27 pm on Oct 11, 2012

Consider this the template and documentation combined... If you want to add fields, add them here too.

Cheers, Mia

You don't have permission to comment on this page.