search

AstunTechnology / iso19139.gemini23

Gemini 2.3 schema plugin for Geonetwork
0 stars 7 forks source link

update XSL transformation to format the gmd:dateStamp to YYYY-MM-DDTHH:MM:SS #149

Closed alexarobu closed 1 month ago

alexarobu commented 1 month ago

This is to match what DGU expects. Stripping out the milliseconds and timezone that gets added in GeoNetwork 4.x

fixes issue #147

alexarobu commented 1 month ago

@archaeogeek I already deployed this to the osmetadata portal and it seems it improved the harvesting to DGU for them.

alexarobu commented 1 month ago

@archaeogeek thank you! :smiley:

alexarobu commented 1 week ago

@archaeogeek :frowning_face: looks like this change introduced an issue in the standard. before this was implemented the gmd:dateStamp was getting automatically updated when you were creating or changing a record, now it gets stuck to whatever is in the record already (the date in the template if it's a new record or the existing date if you edit a record). It's definitely caused by this change because all our portals suffer from this and I tested locally by removing the change and the date gets automatically updated again. I am not entirely sure how to fix it yet, any ideas would be greatly appreciated as always :pray:

PeterParslow commented 1 week ago

Also, data.gov.uk tell me that they've fixed this issue at their end - and you can see some proof of that at https://[ckan.publishing.service.gov.uk/harvest/object/1dd2353a-8400-40e1-babe-7a86b781f2b3](https://ckan.publishing.service.gov.uk/harvest /object/1dd2353a-8400-40e1-babe-7a86b781f2b3)

So for OS, I'd prefer to fix the current issue by removing the fix to this issue.

Longer term, it might be useful to allow people to choose to round their date stamps or not.

alexarobu commented 1 day ago

@PeterParslow I fixed the issue now, please test and let me know if you still face any issues.