User Story #3539 (closed)
Opened 13 years ago
Closed 7 years ago
SA best practices
| Reported by: | jamoore | Owned by: | hflynn |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Documentation | Keywords: | schema |
| Cc: | jburel, ajpatterson | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | 0.5d | Estimated Remaining Time: | n.a. |
Description (last modified by jburel)
- Describe how to use namespace
- What type of SA depending on data to store e.g. for large textual description better to use file annotation instead of comment.
- Provide examples files, maybe use XML mock to generate the files
Change History (5)
comment:1 Changed 13 years ago by jburel
- Cc jburel ajpatterson added
- Description modified (diff)
comment:2 Changed 13 years ago by cxallan
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:3 Changed 11 years ago by ajpatterson
- Component changed from General to Documentation
- Keywords schema added
- Owner set to hflynn
comment:4 Changed 11 years ago by ajpatterson
comment:5 Changed 7 years ago by hflynn
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
This is a ticket to create a page in the formats documentation (probably when it is moved to sphinx) that describes the best way to use Structured Annotations.