-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement publication workflow to codes.wmo.int #6
Comments
I haven't fully figured out how the upload of TTL files to (ci).codes.wmo.int works, the script from "https://github.com/wmo-im/wmds" expects some JSON as input. On the other hand, I have figured out how to adjust makeWMDREntities.py to convert "our" CSVs. Problem is what parameters should we set in the TTL files. They are generated using a textual template that sets "identity", "notation", "label" and "description". So far I have used "Name" for all of them except "description", where I have used "Description" column. But I have no idea where to put our "Source" column. |
Oh, only now have I noticed that @antje-s has created branch |
OK, so she went further than me. Her version of the script puts "Source" into "skos:related" and she made custom versions of other WMDS scripts too. |
Great work here! Note that if the source column is not empty, this means that the codelist value is from an upstream controlled vocabulary. In which case we should use |
Notes from 2024-02-07 meeting with @antje-s / @josusky
Next meeting is on 2024-02-09. |
Updated after our meeting today:
I think we need for PR from csv2registry branch: Many thanks for all the support, I have learned a lot again |
Next steps:
|
The script has been simplified, and a bit of documentation was added. It now uploads files from a directory, so it is not necessary to construct a JSON "uploads" dictionary.
The script has been simplified, and a bit of documentation was added. It now uploads files from a directory, so it is not necessary to construct a JSON "uploads" dictionary.
The script has been simplified, and a bit of documentation was added. It now uploads files from a directory, so it is not necessary to construct a JSON "uploads" dictionary.
* Create generateTTLandCommit.yml * Create makeWCMP2Entities.py toDo - adding column for soure * Create wcmp2-tables.csv * Update wcmp2-tables.csv * Update wcmp2-tables.csv * Create prodRegister * Create testRegister * Create check_urls.py * Create test-gen.py * Create __init__.py * Create generator.py * Create registry.py toDo - publish - userid - publish - post_file * Create generate-readme.py * Update makeWCMP2Entities.py * Update makeWCMP2Entities.py * Update check_urls.py * Update makeWCMP2Entities.py * Update makeWCMP2Entities.py * Update makeWCMP2Entities.py * Update contact-role.csv * Update global-service-type.csv * Update link-type.csv * Update resource-type.csv * Github Action Commit * Update makeWCMP2Entities.py skos:related for our Source links? * Github Action Commit * Update makeWCMP2Entities.py * Github Action Commit * first try to other branch * Update generateTTLandCommit.yml * Update makeWCMP2Entities.py * Update generateTTLandCommit.yml * Update makeWCMP2Entities.py * Update generateTTLandCommit.yml * Update generateTTLandCommit.yml * Update generateTTLandCommit.yml * Update generateTTLandCommit.yml * Update generateTTLandCommit.yml * Update generateTTLandCommit.yml * Update generateTTLandCommit.yml * Delete ttls_wcmp2 directory * Update test-gen.py read registry value from file * Create uploadChanges.py * Update generateTTLandCommit.yml ignore diffs to main in publiacation branch * Update registry.py wis2 - wis in registry-url * Delete scripts/test-gen.py * Delete scripts/registry_deployment directory * Delete scripts/check_urls.py * Delete scripts/generate-readme.py * Update generateTTLandCommit.yml * Update makeWCMP2Entities.py * Delete scripts/uploadChanges.py * Update makeWCMP2Entities.py * Update makeWCMP2Entities.py * Delete prodRegister * Delete testRegister * Add dry-run mode * Add dry run mode to uploadChanges.py * Refactor uploadChanges.py script #6 The script has been simplified, and a bit of documentation was added. It now uploads files from a directory, so it is not necessary to construct a JSON "uploads" dictionary. --------- Co-authored-by: antje-s <[email protected]> Co-authored-by: Jan Osusky <[email protected]>
The plan is to publish everything to the public codes.wmo.int registry with a status of experimental at the beginning of March. This will ensure that all of the links are active when members are reviewing the documents. |
PR update in #10 (see |
update codelist generator/publisher implementation (#6)
Copying notes here for next steps:
|
The codelists2ttl.py no longer generates wis.ttl - we are not going to change this top-level register once the WIS specification is published, so it can remain a manual process. Fixed checking of sub-register existence and a few other minor issues in upload_changes.py.
* fix status handling and a few typos * Fix codelists2ttl.py and upload_changes.py #6 The codelists2ttl.py no longer generates wis.ttl - we are not going to change this top-level register once the WIS specification is published, so it can remain a manual process. Fixed checking of sub-register existence and a few other minor issues in upload_changes.py. * fix merging issue * Update scripts/README.md #6
@david-i-berry suggests using something different than owl:sameAs when the code and definition are copied from another source. |
2024-03-11
Actions: |
Update: this should be ready for publication to codes.wmo.int proper. @amilan17 let us know if this is successful, at which point we can close this issue. |
Note that the authenticate part of upload_changes needs to be modified to use port 443 at: wcmp2-codelists/scripts/upload_changes.py Line 46 in 6b9eab5
i.e.
|
Thanks @david-i-berry. The result is the same whether 443 is explicitly set or not. |
I agree with @tomkralidis, port 443 is default for HTTPS. Only if a non-standard port, let say 8181 is used, it needs to be explicitly set. |
I was able to upload AFTER removing the global-service-type TTLs. For some reason, the software does not accept those, but the TTLS are identical to the accepted TTLS accept for the content referring to global-service-type... ?! |
Hi Anna,
I am checking the issue with global-service type sub-register, the server
is responding with with an internal error when I try to GET (read) the
resource:
$ curl https://ci.codes.wmo.int/wis/global-service-type/
Cannot invoke "com.epimorphics.registry.core.Description.getRoot()" because
the return value of
"com.epimorphics.registry.store.StoreAPI.getCurrentVersion
(String)" is null
I will try to remove this sub-register and retry.
JanO
…On Thu, Mar 28, 2024 at 4:13 PM Anna Milan ***@***.***> wrote:
I was able to upload AFTER removing the global-service-type TTLs. For some
reason, the software does not accept those, but the TTLS are identical to
the accepted TTLS accept for the content referring to
global-service-type... ?!
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFS4LF6LXUEVD4SDF5SDHW3Y2QQR3AVCNFSM6AAAAABCVCN44OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGQ3DOOBWGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, I get the same error when trying to upload ValueError: Cannot upload to https://ci.codes.wmo.int/wis/global-service-type: 500 : Cannot invoke "com.epimorphics.registry.core.Description.getRoot()" because the return value of "com.epimorphics.registry.store.StoreAPI.getCurrentVersion(String)" is null |
I am afraid that the removal of sub-register did not help, I am still
getting the internal server error.
…On Thu, Mar 28, 2024 at 4:31 PM Anna Milan ***@***.***> wrote:
Yes, I get the same error when trying to upload
ValueError: Cannot upload to
https://ci.codes.wmo.int/wis/global-service-type: 500 : Cannot invoke
"com.epimorphics.registry.core.Description.getRoot()" because the return
value of
"com.epimorphics.registry.store.StoreAPI.getCurrentVersion(String)" is null
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFS4LF76Q5O6JJJOZZDSYE3Y2QSTRAVCNFSM6AAAAABCVCN44OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGUYDMMBVGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The error message changed a bit over the weekend, now it reveals less of the internal information, but it is still an "Internal Server Error". I don't think we can fix this from our side. @amilan17 could you please contact the server administrator and request help? BTW, I have created a register "wis2" (https://ci.codes.wmo.int/wis2) and successfully uploaded all codes to it. |
@josusky how did you manage to successfully upload all codes? The error didn't prevent that on the wis2 registry? |
It seems that the problem somehow related to the |
Codelists are now published to https://codes.wmo.int/ with the status of Experimental. |
Examples:
The text was updated successfully, but these errors were encountered: