Eli Chadwick

Technical notes: This error arises when an IntegrityError occurs while handling a signup: https://github.com/carpentries/amy/blob/39f9544c8edfc50a3abc9a3fc5d07f77d7d71cfd/amy/recruitment/views.py#L375-L396 I _think_ we can expect most (if not all) of these IntegrityErrors to come from a...

Adding to accessibility project as this affects cognitive load

Hi @chayim @WisdomPill, I was going to raise an issue here to bump Redis in light of the recent vulnerability https://github.com/redis/redis-py/issues/2665 but found this pre-existing PR. Any chance of getting...

I just ran into this also. It would be useful for the local tool template to loop through the tool directory looking for XML files if you can determine that...

Help text: > A link to the activity, if there is one. If you served at a workshop, enter the workshop website. If you made a GitHub contribution, ensure your...

> the `jsonld` files are inconsistent This is because the spec changed between 1.0 and 1.1 about the naming of the metadata file. 1.0 requires `ro-crate-metadata.jsonld`, 1.1+ requires `ro-crate-metadata.json` -...

@dgarijo would adding `Options +FollowSymLinks` to the `.htaccess` resolve the problem? Like in https://github.com/perma-id/w3id.org/blob/master/.htaccess

Actually, I think this is a problem with the `ro-crate-metadata.json` symlink in 1.1 - neither GitHub nor my file system recognises it as a symlink. The one in 1.2-DRAFT seems...

#361 should fix it on the website side. @dgarijo when you update the `.htaccess` can you ensure it goes to ``` https://www.researchobject.org/ro-crate/specification/$1/ro-crate-metadata.jsonld ``` not ``` https://www.researchobject.org/ro-crate/$1/ro-crate-metadata.jsonld ``` for forward compatibility

Fixed by #276