-
Improvement
-
Resolution: Invalid
-
Normal
-
None
-
None
-
None
For releases there is a checkbox to mark releases that indeed have no barcode (as opposed to the data just missing / being unknown).
This flag is not available in the webservice. Take for example the release https://musicbrainz.org/release/2c59ca24-d4ed-4265-94cf-14c65c62daa9/ . The web service response (https://musicbrainz.org/ws/2/release/2c59ca24-d4ed-4265-94cf-14c65c62daa9?inc=aliases%2Bartist-credits%2Blabels%2Bdiscids%2Brecordings&fmt=json) provides the barcode as an empty string, but from the data it is not clear whether barcode is just empty or marked as non-existing.
Maybe there could be a boolean "no-barcode" field. This info is a requirement for PICARD-2799
- is a dependency of
-
PICARD-2799 Save barcode as "[none]" when "release does not have a barcode" is checked
-
- Blocked
-
AFAICT the flag is available, as in that barcode: "" means none. Compare https://musicbrainz.org/ws/2/release/d749bc0d-f7cb-4f0e-a7cb-6ff93a2d1311?inc=aliases%2Bartist-credits%2Blabels%2Bdiscids%2Brecordings&fmt=json (unset) which has barcode: null.
Same for XML, where none is shown as "<barcode/>" while unset just has no barcode element at all.
If this is not good enough for Picard and it should still be marked in a different way, feel free to reopen and reword a bit with what you would need for it to work properly.
FWIW, I'd also be fine with reopening this for ws/3 and rename it to something like "Indicate no barcode status more clearly in ws/3"