Undesirably forced submission tags #217

New issue

Closed

opened 2026-06-24 05:05:34 +00:00 by mih · 3 comments

mih commented

2026-06-24 05:05:34 +00:00

Owner

I created a collection via

curl -X 'POST' \
  'http://localhost:8000/collections' \
  -H 'accept: application/json' \
  -H 'X-DumpThings-Token: some' \
  -H 'Content-Type: application/json' \
  -d '{
  "default_token": "token1",
  "curated": "curated1",
  "schema": "things.yaml",
  "incoming": "inbox1",
  "backend": {
    "type": "record_dir+stl",
    "mapping_method": "digest-md5"
  },
  "auth_sources": [
    {
      "type": "config"
    }
  ],
  "name": "collection1"
}'

Notice the absence of any submission_tags.

However, when I query the collections, I get

{
  "collection1": {
    "default_token": "token1",
    "curated": "curated1",
    "schema": "things.yaml",
    "incoming": "inbox1",
    "backend": {
      "type": "record_dir+stl",
      "mapping_method": "digest-md5"
    },
    "auth_sources": [
      {
        "type": "config"
      }
    ],
    "audit_backends": [],
    "submission_tags": {
      "submitter_id_tag": "http://purl.obolibrary.org/obo/NCIT_C54269",
      "submission_time_tag": "http://semanticscience.org/resource/SIO_001083"
    },
    "use_classes": [],
    "ignore_classes": []
  }
}

I interpret this as: one can not turn off record tagging, one can only decide the specific tags that will unconditionally be attached.

This is undesirable, because forcing content into records that a user did not submit has been a source of problems for quite some time. It should be possible to turn this off.

I created a collection via ``` curl -X 'POST' \ 'http://localhost:8000/collections' \ -H 'accept: application/json' \ -H 'X-DumpThings-Token: some' \ -H 'Content-Type: application/json' \ -d '{ "default_token": "token1", "curated": "curated1", "schema": "things.yaml", "incoming": "inbox1", "backend": { "type": "record_dir+stl", "mapping_method": "digest-md5" }, "auth_sources": [ { "type": "config" } ], "name": "collection1" }' ``` Notice the absence of any `submission_tags`. However, when I query the collections, I get ```json { "collection1": { "default_token": "token1", "curated": "curated1", "schema": "things.yaml", "incoming": "inbox1", "backend": { "type": "record_dir+stl", "mapping_method": "digest-md5" }, "auth_sources": [ { "type": "config" } ], "audit_backends": [], "submission_tags": { "submitter_id_tag": "http://purl.obolibrary.org/obo/NCIT_C54269", "submission_time_tag": "http://semanticscience.org/resource/SIO_001083" }, "use_classes": [], "ignore_classes": [] } } ``` I interpret this as: one can not turn off record tagging, one can only decide the specific tags that will unconditionally be attached. This is undesirable, because forcing content into records that a user did not submit has been a source of problems for quite some time. It should be possible to turn this off.

mih commented

2026-06-25 06:06:38 +00:00

Author

Owner

Still the case with v6.2

mih referenced this issue

2026-06-25 06:22:48 +00:00

Curation workflow gap #163

mih referenced this issue from orinoco/shacl-vue

2026-06-28 10:18:32 +00:00

Failure to submit due to duplicate and conflicting annotations #360

cmo commented

2026-06-29 07:02:26 +00:00

Owner

A simple solution would be to do the following

remove the forced submission annotations
add a query parameter, e.g. auto-annotate, which ---if set--- leads to the generation of submission tags.

Unless there is disagreement, I will implement this behavior

A simple solution would be to do the following - remove the forced submission annotations - add a query parameter, e.g. `auto-annotate`, which ---if set--- leads to the generation of submission tags. Unless there is disagreement, I will implement this behavior

cmo referenced this issue

2026-06-29 09:25:34 +00:00

Do not create automated submission-tags by default #240

cmo commented

2026-06-29 11:51:40 +00:00

Owner

Fixed in release 6.3.0

cmo closed this issue

2026-06-29 11:51:40 +00:00