Incorrect source path in generated LL for implicit container #89

New issue

Open

opened 2026-10-14 20:14:25 +00:00 by scossu · 0 comments

scossu commented

2026-10-14 20:14:25 +00:00

Owner

If I submit a LL such as:

content_type,id,source_path
still_image,RND001,data/img1.tif

This creates a still_image implicit container with the given RND001 ID, and a still_image_file member with a new random ID, let's say RND002. So far so good; but the source path of the container is set to RND0001, and the one of the image to data/RND0001/img1.tif. This is wrong because a generated LL cannot be submitted using the original file paths:

content_type,id,source_path
still_image,RND001,data/RND001
still_image_file,RND002,data/RND001/img1.tif

The source path of the container should be empty and the one of the image the same as the original LL:

content_type,id,source_path
still_image,RND001,
still_image_file,RND002,data/img1.tif

If I submit a LL such as: ``` content_type,id,source_path still_image,RND001,data/img1.tif ``` This creates a `still_image` implicit container with the given `RND001` ID, and a `still_image_file` member with a new random ID, let's say `RND002`. So far so good; but the source path of the container is set to `RND0001`, and the one of the image to `data/RND0001/img1.tif`. This is wrong because a generated LL cannot be submitted using the original file paths: ``` content_type,id,source_path still_image,RND001,data/RND001 still_image_file,RND002,data/RND001/img1.tif ``` The source path of the container should be empty and the one of the image the same as the original LL: ``` content_type,id,source_path still_image,RND001, still_image_file,RND002,data/img1.tif ```

scossu added this to the v1.1.0 milestone

2026-10-14 20:14:25 +00:00

scossu added the

area/submission

bug

high

labels

2026-10-14 20:14:25 +00:00

scossu added the

area/integrity

label

2026-10-15 02:05:41 +00:00