landreev

Same here (at IQSS), we haven't been using it much because of how much of a nuclear option it is, with all the human guest users being the collateral damage....

@jp-tosca Thank you for making the retroactive fixes to the 6.1 release note. Did you only fix the 2 things you specifically noticed, or did you copy-and-paste the complete source...

@qqmyers the upgrade instruction is just saying "update these 4 metadata blocks:" now. We usually say why we are asking people to do that. Is that to resolve any potential...

OK, I just looked at #9983 and it focused on the missing constraints, so I assumed #9984 was just to address that. I would maybe just say "Update the following...

There is an extra issue @scolapasta pointed out in #10937 that I'm adding as task 3. here - in the current scheme of things the set name is stored in...

@ofahimIQSS Sorry for the delay, I pretty much forgot about this PR. The fact that the 2 files are differently formatted in the DDI output is simply because only the...

Thank you for the report @nightowlaz! Yes, this is definitely one extra reason to get rid of that curl command in the implementation. I'm going to try and get this...

The PR looks great, I meant to merge it last night. I didn't go out of my way trying things to break it; but all the valid json files I...

@stevenwinship There are 3 extra .tab files in `scripts/api/data/metadatablocks/iso-639-3_Code_Tables_20240415` (`iso-639-3-macrolanguages.tab` etc.). Are these checked in for reference purposes? (or, are they checked in on purpose?)

In the light of having confirmed that having the full list in the CV does not make the UI unusable, I would at least consider adding it in full to...