Daniel-KM

As usual, if you want I push it directly in Omeka, just tell me. There are so many pr, features, fixes or issues, of me or not, that are fixed...

I forgot: it made it available via module [shortcode](https://gitlab.com/Daniel-KM/Omeka-S-module-Shortcode) too, and any other metadata of any resource in fact.

I pushed a pull request some years ago (#1260) to avoid to override the default js, so it was possible simpler. Currently, I use a js that bypass this point,...

Rebased.

Rebased on 1.3. Available via module [Next](https://github.com/Daniel-KM/Omeka-S-module-next).

Rebased on 1.4. Available via module [Next](https://github.com/Daniel-KM/Omeka-S-module-next).

Merged with laminas.

I didn't noted the url last month, so I don't remember where it crashes. Probably related to a module, but the fix was in the core.

Indeed, a post should be one resource. So to keep the rest semantics, it's possible to add some intermediate urls to manage collections, like /api/resource-collection (https://stackoverflow.com/questions/411462/restful-way-to-create-multiple-items-in-one-request#33768160). It's probably not possible...

The main usage is messenger and logger. I don't have any other usage currently.