You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.rst
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,9 +48,29 @@ Development
48
48
49
49
The most convenient way to develop on HistomicsUI is to use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops>`_.
50
50
51
+
Annotations and Metadata from Jobs
52
+
----------------------------------
53
+
54
+
This handles ingesting annotations and metadata that are uploaded and associating them with existing large image items in the Girder database. These annotations and metadata re commonly generated through jobs, such as HistomicTK tasks, but can also be added manually.
55
+
56
+
If a file is uploaded to the Girder system that includes a ``reference`` record, and that ``reference`` record contains an ``identifier`` field and a ``fileId`` field, specific identifiers can be used to ingest the results. If a ``userId`` is specified in the ``reference`` record, permissions for adding the annotation or metadata are associated with that user.
57
+
58
+
Metadata
59
+
========
60
+
61
+
Identifiers ending in ``ItemMetadata`` are loaded and then set as metadata on the associated item that contains the specified file. Conceptually, this is the same as calling the ``PUT`` ``item/{id}/metadata`` endpoint.
62
+
63
+
Annotations
64
+
===========
65
+
66
+
Identifiers ending in ``AnnotationFile`` are loaded as annotations, associated with the item that contains the specified file. Conceptually, this is the same as uploaded the file via the annotation endpoints for the item associated with the specified ``fileId``.
67
+
68
+
If the annotation file contains any annotations with elements that contain ``girderId`` values, the ``girderId`` values can be ``identifier`` values from files that were uploaded with a ``reference`` record that contains a matching ``uuid`` field. The ``uuid`` field is required for this, but is treated as an arbitrary string.
69
+
70
+
51
71
Funding
52
72
-------
53
-
This work is funded in part by the NIH grant U24-CA194362-01_.
73
+
This work was funded in part by the NIH grant U24-CA194362-01_.
0 commit comments