Florian M
Florian M
I don’t think we can easily reuse the displayName, because several existing values contain spaces and parentheses etc. Unless we decide that we can just drop/convert these. If we want...
Another thought: since we still need the nameOnDisk anyway, could we not use that for most APIs as well? e.g. in datastore and worker jobs. We could just make the...
Thoughts - dataset id also needs to be serialized to NMLs - heuristic to select dataset from ambiguous names: take the oldest (hypothesis: old NMLs/URIs were generated _before_ the renaming...
Could you check if the mappings really affect this or if it is the case for all volume annotations with fallback layer? I think this green border used to be...
Sorry I could not find all the right threads here to reply to, these are my latest notes on the open questions: - [x] TaskCreationParameters: let’s do the api adapter...
> In the datasource-properties there is a field [`"id"`] which is not changed if the dataset name is changed. Is this intentional? This is ok from my side. The backend...
> The libs currently do not consider the path name but use the id field of the datasource-properties.json file for accessing the name of the dataset. So the getter and...
> I checked routes that needed adaptation and came up with that the following do not need adaptation or do they? Looks right to me!
:tada: :crossed_fingers:
I investigated a bit and it turns out the reupload has nothing to do with it. It is just generally allowed to load precomputed meshes after brushing. It will of...