Aim:
Introduction of UIDs for Objects in MITK (current scope Nodes and BaseData-derived ones). This should allow to uniquely reference/identify data (e.g. in the context of DICOM).
Aim:
Introduction of UIDs for Objects in MITK (current scope Nodes and BaseData-derived ones). This should allow to uniquely reference/identify data (e.g. in the context of DICOM).
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | floca | T23721 Project "Astonishing Angelfish" | ||
Resolved | kislinsk | T23736 Introduction of UIDs for data/nodes etc | ||
Resolved | kislinsk | T23740 Introduce IDs to BaseData | ||
Resolved | kislinsk | T23743 Introduce mitkNodePredicateID and mitkNodePredicateDataID | ||
Resolved | kislinsk | T23737 Introduce IIdentifiable | ||
Wontfix | kislinsk | T23744 Implement specific UID strategy for mitk::Image | ||
Wontfix | kislinsk | T23745 Specify image UID generation method | ||
Resolved | kislinsk | T23750 Implement IIdentifiable for mitk::DataNode | ||
Resolved | floca | T23741 Specify default UID generation method |
Yes. Currently I use it in the domain specific solutions. But it got a very weak Implementation. If we use it, it should be reworked in T23741.
I also used a different UID-Generation in my SemanticRelations Module (based on boost/uuid). As this might not be necessary in the future when using UIDs for objects, it would be desirable to have a common UID Generator in MITK (see T14333).
I merged all branches of resolved subtasks into the branch of this task. UID generation is currently done by mitk::UIDGenerator. I suggest to improve/adapt this class to resolve the remaining subtask T23741: Specify default UID generation method.