Difference between revisions of "ESciDoc Admin Tool"
Jump to navigation
Jump to search
Haarlaender (talk | contribs) m |
m (→Requirements) |
||
Line 16: | Line 16: | ||
** plugin interface to extend support for solutions | ** plugin interface to extend support for solutions | ||
*** Maybe like a set of managers (one for managing users, one for contexts etc.) with user interfaces that can be "pre-configured". Means certain values are preset by the current solution. --[[User:Haarlaender|Haarlaender]] 15:12, 19 October 2009 (UTC) | *** Maybe like a set of managers (one for managing users, one for contexts etc.) with user interfaces that can be "pre-configured". Means certain values are preset by the current solution. --[[User:Haarlaender|Haarlaender]] 15:12, 19 October 2009 (UTC) | ||
*check on more light-weight technology esp. for the GUI | |||
*1&1 GUI widgets | |||
*Groovy, Grails | |||
*GWT - javascript too cryptic, widgets compared to what other FW provide | |||
*javaScript based | |||
*portal/portlets | |||
*todo: evaluation of FWs |
Revision as of 12:50, 20 October 2009
eSciDoc Admin Tool[edit]
The Admin Tool shall support administrative tasks for eSciDoc infrastructure and solutions. Information on initial implementation available at ESciDoc Admin Tool initial implementation
Requirements[edit]
- functions
- administrate core and solutions
- create/alter roles
- control re-cache/re-index
- implementation
- GUI
- Style should be easily changeable and be based current solutions. --Haarlaender 15:12, 19 October 2009 (UTC)
- CLI (?)
- I don't think this is necessary as an additional abstraction layer. There is still the SOAP and REST interface --Haarlaender 15:12, 19 October 2009 (UTC)
- plugin interface to extend support for solutions
- Maybe like a set of managers (one for managing users, one for contexts etc.) with user interfaces that can be "pre-configured". Means certain values are preset by the current solution. --Haarlaender 15:12, 19 October 2009 (UTC)
- GUI
- check on more light-weight technology esp. for the GUI
- 1&1 GUI widgets
- Groovy, Grails
- GWT - javascript too cryptic, widgets compared to what other FW provide
- javaScript based
- portal/portlets
- todo: evaluation of FWs