Task #371 (closed)
Implement ExternalInfo (LSIDs, etc.)
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0-M3 |
| Component: | Security | Version: | 3.0-M1 |
| Keywords: | iteration6 | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
All the information which is contained in Details needs to be properly handled by the security system. External links play a similar role to events and, therefore, need to be taken care of now, even if the LSID import/export functionality comes later.
Change History (3)
comment:1 Changed 18 years ago by jmoore
comment:2 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
r975 closes:
- Implements ExternalInfo security logic and integration test
- Reworks HibernateUtils and adds an initial unit test
- Added optional ExternalInfo string to Details.toString()
Rather than being a component, ExternalInfo is a one-to-one (or a many-to-one with a unique constraint) with cascade="delete" enabled. The semantics are similar.
comment:3 Changed 18 years ago by jmoore
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r972 implements the basic functionality for ExternalInfo (tables, class, Details changes). Still needs to be added to the security infrastructure.
Note: ExternalInfo may should be an embedded component that gets deleted on removal.