eossr upload unique function

• unique function to upload to the ossr regardless of new record or new version
• unit test
• update doc and snippets
• check if the record does not already exist in case record id not passed
• remove previous scripts and snippets

changed the description

added 1 commit

• 46897fb8 - add unit test

Compare with previous version

marked the checklist item unit test as completed

added 1 commit

• 33dae94b - return published request

Compare with previous version

added 1 commit

• c62ca541 - raise error if entry not created

Compare with previous version

added 1 commit

• 9f0a3183 - assert file creation ok

Compare with previous version

added 1 commit

• 9397e225 - come on

Compare with previous version

added 1 commit

• 44312f81 - actually write in the file

Compare with previous version

added 1 commit

• ff51104e - test

Compare with previous version

added 1 commit

• 8960832a - test

Compare with previous version

added 1 commit

• 09bd06aa - fix

Compare with previous version

added 1 commit

• 0a62ae30 - common function to upload directory content

Compare with previous version

added 1 commit

• d75ff430 - clean comments

Compare with previous version

added 1 commit

• 7c822ab0 - adapt documentation to unique upload script

Compare with previous version

marked the checklist item update doc and snippets as completed

marked this merge request as ready

added 1 commit

• 08531ff7 - renaming snippets for ordering

Compare with previous version

changed the description

This is ready to review @garcia However, I was not sure what was the best approach for the documentation:

• keep it intact and don't make snippets using that unique function
• entirely remove the previous snippets and make a new unique one
• keep both

What do you think will be the less confusing and simplest for users?

marked this merge request as draft