Peter Sefton

@amoeba Calcyte documentation is really lacking I'll try to get on to that ASAP, but meanwhile if you want some help, let me know. I worked with @cameronneylon on his...

@amoeba Just pushed an update to Calcyte to fix tests and a bug creating new spreadsheets. The idea for the spreadsheets came from Mike Lake (@speleolinux) on a previous project;...

Re the structure of Calcyte spreadsheets - we used xlsx because it supports multiple workbooks, meaning you can have tables of people, places, equipment etc. (But calcyte is not the...

I've had a go at transforming Dataspice metadata into datacrate metadata to see what happened. I wrote a quick script to transform the metadata to the DataCrate standard (flattened JSON,...

@cboettig Thanks Carl - I'll fix the URLs to be canonical in the spec. @amoeba We specified the flattened format because it is MUCH easier for programmers to work with...

@cboettig Processing / traversing has so far mostly been limited to generating the HTML pages for DataCrate, parsing DataCrates for upload. Here's a little hack I did for a conference...

Just retested this with 3.1.1 - it's still happening @dlongley I can't see how to re-open this.

An api endpoint that would take a fully qualified property URI and return a property ID would be really useful. Is there one?

Thanks @zerocrates that works. Specifically: http://localhost/api/properties?term=dcterms%3Acreator&key_identity=your-id&key_credential=your-key Returns [{"@context":"http:\/\/localhost\/api-context","@id":"http:\/\/localhost\/api\/properties\/2","@type":"o:Property","o:id":2,"o:local_name":"creator","o:label":"Creator","o:comment":"An entity primarily responsible for making the resource.","o:term":"dcterms:creator","o:vocabulary":{"@id":"http:\/\/localhost\/api\/vocabularies\/1","o:id":1}}]

In the short term it would be worth explaining this in the API docs, spelling out that the terms used in the JSON examples are placeholders and it's o:id that...