User Story #10232 (new)
Opened 11 years ago
Dataset:Image ONE-to-many
Reported by: | wmoore | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Unscheduled |
Component: | General | Keywords: | n.a. |
Cc: | jamoore, cxallan, jburel | Story Points: | n.a. |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Images can be in multiple Datasets for historical reasons. This is not a feature that is used by anyone now, as far as I know. But it creates a LOT of extra work for developers and users are confused when they come across this.
We could add "unique" to child in the Dataset-Image-Link table, so there's only 1 link per image. This wouldn't need a change to the Model or any queries.
We'd need a DB upgrade script so admins could choose (or just randomly pick) a parent for each Image that is currently in 2 Datasets (probably not very many).
Many existing calls, E.g. BlitzGateway? Image.getParent() already assume a single parent and would continue to work with no changes.
All the above also applies to Project:Dataset links too.