anzsoildata / aus-vocab Goto Github PK

Hi @abhritchie
The main thing is that I'd like Jonathan and Simon to have edit rights. Under settings this seems to go across both repos. If you could have a look for me that would be great.

We have one ‘retired’ and some ‘superseded by’ (and those that have replaced the superseded terms)
Here, they are in skos:note for example - "14G2 has been superseded by 14G2a and 14G2b in Soil Chemical Methods Australasia, Rayment G.E. and Lyons D.J. ISBN 9780643101364"@en;
Do we need to deal better with this in the upload files, or is this work that is done in LDR after upload?

Noting from email @drshorthair 26042021 for resolution by Megan
Might be worth using a link instead of just the ISBN number.
The Publisher’s page for the book is https://www.publish.csiro.au/book/6418
And this gets a JSON description of the Google books version https://www.googleapis.com/books/v1/volumes?q=isbn:9780643102187
Or we could use the ISBN URN scheme – i.e. these two

URN:ISBN:978-0-643-10218-7
URN:ISBN:978-0-909605-68-1

See https://www.iana.org/assignments/urn-formal/isbn and https://www.myidentifiers.com.au/identify-protect-your-book/isbn/converter-tool

I’m looking here for a more formal/universal notation for ISBN.

Hey @meganrwong - this repository is current private. I erred on the side of caution when creating it. Let me know if you want it switched to public. Or, you can do it yourself in the 'Danger Zone' in this repo's settings.

I strongly suggest having a separate GitHub repository per vocabulary.
The title of this repo suggests that you plan to manage multiple aus-vocabs all in the same repo.
That is likely to see everything get a bit too tangled up.

From @dr-shorthair 19 Mar 2021
To make it easy to load in the sandbox and then transfer to the permanent location, the entries should have local identifiers, for example

<1A2> a skos:Concept, sosa:Procedure;
  dct:description "Field sampling - diagnostic"@en;
  dct:identifier "http://anzsoil.org/def/au/scma/1A2"^^xsd:anyURI;
  dct:source "ISBN 9780643101364"@en;
  rdfs:label "Field sampling - diagnostic"@en;
  skos:definition "Field sampling - diagnostic"@en;
  skos:inScheme <>;
  skos:member <1> ;
  skos:notation "1A2";
  skos:prefLabel "Field sampling - diagnostic"@en;
  skos:topConceptOf <> .

However, it doesn’t look like SKOS-Play! Will do this, so there may have to be a post-processing edit (I do this routinely when loading into the LDR.)

This regex will make the change the s: identifiers throughout the file –

Find s:([0-9][0-9a-zA-Z]*)
Replace <$1>

The orange in the Excel version 001.

rdf:type indicates concepts which I wondered if they were strictly 'procedures'. In the green book, if you have access to, you will see that their descriptions contain some information required to carry out the narrower procedures - ie the will tell you how to handle chemicals, steps that must be taken prior to conducting narrower procedures, why you would select one procedure over another in certain conditions, how to interpret results etc.

I have them as sosa:Procedure, skos:Concept.

I'm just noting this here as an issue and how I have addressed in v 001.

No defs in
Access to online text required for copy/paste.
Also, defs are very lengthy.
skos:label used as skos:definition placeholders