Version 4 (modified by lawrence, 15 years ago) (diff) |
---|
The MOLES Portal
... is really just the browse interface to MOLES records.
Overall Use Case
Layered Architecture
- The exist databases at all sites need to be secured so that only locally running processes can access them.
- That locally running process could exploit Kev's new code which accesses the database.
- and expose two interfaces - the direct GUI interface, and
- a web service interface that a remote GUI interface can access.
- Note that Kev's current code doesn't respect any access control at all!
- It is possible that a local gui instance could use the remote web service interface).
Current Tickets
- #25
- Resources for MOLES browse GUI work
- #38
- Simple webservice for retrieving a single Stub-b
- #46
- XSLT to shape stub-b for portal
- #47
- MOLES browse architecture
- #180
- browse to a non-existent uri hangs
- #181
- browse get data icon should only appear for data entites
- #182
- browse history needs to work off a cookie
- #183
- need to make browse icons etc configurable
- #184
- [m] massive numbers of related entities in moles
- #193
- [M] Moles browse needs to tell user when data is secure
- #240
- [S] Need a simple attribute authority client