User Story #2622 (new)
Opened 14 years ago
Last modified 14 years ago
Evaluate using high-level graphs names for delete, export
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | jburel, ajpatterson | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
As with the schema, we are in the process of defining various compliance specifications which describe graphs of objects which belong together. The IDelete and Exporter interfaces could use these specifications as a way to define which objects, starting from some arbitrary object, should be deleted, exported, etc.
Change History (2)
comment:1 Changed 14 years ago by jmoore
comment:2 Changed 14 years ago by jmoore
- Type changed from Task to User Story
Changing into a story as part of phase II requirement (#2911)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
For the moment, the specifications are handled in spec.xml (as mentioned in #2615) in Spring XML. In the future, we may want do this in the Schema itself.