Member

Hi all, I direct Open Context (http://opencontext.org) and collaborate with the Digital Index of North American Archaeology (DINAA) project (http://ux.opencontext.org/archaeology-site-data/).

I’m interested in meeting and collaborating with folks creating, curating and using State Government data.

Hi Alice Lynn,

Sounds great. Once you’ve put your data through Refine and feel like it is clean and consistent, please do send it on to us. We can provide another outside editorial eye, and then start working with you on peer review. It seems like your content will be in multiple places, so we’ll want to cross-reference so that we link all the…[Read more]

Hi Ann,

I’d tend to shy away from a license like CC BY-NC-SA. That is a very restrictive license, and does not qualify as “open data”. It would mean virtually no reuse, especially since nobody knows what “commercial” really means. I would be ok with that for indigenous materials, since the ethics would mean stakeholder concerns should come first.…[Read more]

Hi All,

To get you all started, I have a simple (ugly) demo of API search functionality here:

http://ekansa.github.io/simple.html

It’s just a start, but the example should be really useful for you all to adapt. You can test it with a search for “glass” or “bottle” to see that it works.

Good luck!
-Eric

Sara + Nancy,

One more thing, here’s the JSON result with the thumbnails included. I forget to specify that they needed to be specifically requested with the parameter “attributes=thumbnail”:

http://opencontext.org/subjects-search/.json?prop=oc-gen-cat-object&proj=91-historic-fort-snelling&response=metadata,uri-meta&attributes=thumbnail

Nancy, my examples about the Ecuador pottery apply just as much to you. The only difference is that the URL for your materials has parameters with different values that correspond to your specific dataset.

To start, here’s an HTML view of objects in your…[Read more]

(1) On the downloadable data side, it would probably be easiest if Open Context generated a CSV dump of the data. I will be happy to prepare that dump once the data are in a final state (no longer actively edited). One can just link to the CSV data download.

(2) For pictures, there are links to thumbnail images in the JSON search results (if the…[Read more]

For searching, you’ll probably want to use the simple version of the API to get simple JSON results. JSON is easy to work with in Javascript to display as you like.

For instance, if you start with an HTML search of your pottery, here’s the…[Read more]

<p>One request was to have a search function to query Open Context and display results. This is well supported, but you need to understand something about how Open Context’s search API works. There are two main types of results for each search query:</p>

Facets: Facets summarize metadata applicable to the entire set of results. For instance,…[Read more]

I have no idea how your data are structured and what your tables are. So not knowing your schema, it’s hard to respond to this. But, there are often many, many ways to relate data using SQL. Besides JOINs there are sub-queries (see: http://www.postgresqltutorial.com/postgresql-subquery/). Some of these approaches work differently on different…[Read more]

What Dan said… 🙂

Anyway, probably the best thing to do is look at the examples that illustrate how CSV plugins for Leaflet work in practice. Normally the people that write the plugins have some demo pages, and those are usually the best places to start in figuring out how to use the plugin.

That said, there are lots of different programming…[Read more]

Cool!

A few notes of response:

(1) Yes the Turkish diacritical marks are OK in Open Context (any UTF-8 characters work), the only issue I’ve seen is getting Excel to read the UTF-8 correctly with CSV dumps from Open Context. Libre Office handles it just fine, but Excel chokes on them.

(2) Not all of your fields will map cleanly to Dublin Core.…[Read more]

Hi Nancy,

<p>I’ve reviewed your dataset and it looks great! I added a few URIs for Encyclopedia of Life taxa and UBERON for the mandibles, and I also expanded out some abbreviations (AAT, etc.). So I’m more or less ready to import.</p>

<p>However I wanted to check with you about the spatial + stratigraphic organization of the data. I don’t see…[Read more]

Great! OK. When you a ready with the images, it’s probably easiest to make a table with a manifest of image file names, identifiers for the objects they describe, and any metadata you may have on the images (photographer, title, orientation, type of image, etc.). Dropbox is probably the easiest way to go.

I should have time tomorrow to prepare…[Read more]

Hi Nancy,

I finally had a chance to look at the revisions in detail. They look really good to me, I especially appreciate how you updated the date fields to be internationally unambiguous. I see a few minor issues (for example I should probably normalize “surface” and “Surface” in the Vertical Reference Point field.), but these are easy for me t…[Read more]

Hi Nancy,

I finally had a chance to look at the revisions in detail. They look really good to me, I especially appreciate how you updated the date fields to be internationally unambiguous. I see a few minor issues (for example I should probably normalize “surface<span class=”facet-choice-count”>” and “</span>Surface<span c…[Read more]

Awesome! I’m glad it worked!

🙂

Hi Nancy,

The Getty has some nicely documented help. Here is their “how-to” on running searches on any label (preferred or alternate) in SPARQL:

(SPARQL examples, Section 2.15)

For an Open Refine recipe, try this in when Creating a new Column by Fetching URLs:

“http://vocab.getty.edu/sparql.json?query=select+*+%7B%3Fsubj+rdfs%3Alabel+%22” +…[Read more]