I scanned the front and back of a book. These were each identified separately and were given different valuations.
What did you expect to happen?
I guess I expect there to be some way to associate the front and back of a single item -- e.g. a book, vinyl, trading card, etc. but also other objects with this property. I know it'll be hard for suppressing duplicates vs. identifying multiple instances of an object, but it looks like in the UI we tell the user to increment Quantity in the single record vs. scanning multiple instances of an object. (I'm not sure how we'd handle multiple instances of an object but with individually different condition attributes; maybe these would have to be separate scans/records.
Steps to reproduce
Open the catalog, navigate to the Tote containing these items. In the row-based listing of Tote contents, the valuation data (and some other attributres) appear different where the plates are just front and back of a single image.
Where did this happen?
Desktop (web browser)
Device and browser
No response
Screenshots or photos
No response
Ditto version
No response
### What happened?
I scanned the front and back of a book. These were each identified separately and were given different valuations.
### What did you expect to happen?
I guess I expect there to be some way to associate the front and back of a single item -- e.g. a book, vinyl, trading card, etc. but also other objects with this property. I know it'll be hard for suppressing duplicates vs. identifying multiple instances of an object, but it looks like in the UI we tell the user to increment Quantity in the single record vs. scanning multiple instances of an object. (I'm not sure how we'd handle multiple instances of an object but with individually different condition attributes; maybe these would have to be separate scans/records.
### Steps to reproduce
Open the catalog, navigate to the Tote containing these items. In the row-based listing of Tote contents, the valuation data (and some other attributres) appear different where the plates are just front and back of a single image.
### Where did this happen?
Desktop (web browser)
### Device and browser
_No response_
### Screenshots or photos
_No response_
### Ditto version
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What happened?
I scanned the front and back of a book. These were each identified separately and were given different valuations.
What did you expect to happen?
I guess I expect there to be some way to associate the front and back of a single item -- e.g. a book, vinyl, trading card, etc. but also other objects with this property. I know it'll be hard for suppressing duplicates vs. identifying multiple instances of an object, but it looks like in the UI we tell the user to increment Quantity in the single record vs. scanning multiple instances of an object. (I'm not sure how we'd handle multiple instances of an object but with individually different condition attributes; maybe these would have to be separate scans/records.
Steps to reproduce
Open the catalog, navigate to the Tote containing these items. In the row-based listing of Tote contents, the valuation data (and some other attributres) appear different where the plates are just front and back of a single image.
Where did this happen?
Desktop (web browser)
Device and browser
No response
Screenshots or photos
No response
Ditto version
No response