[
https://jira.duraspace.org/browse/DS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28443#comment-28443
]
Bram Luyten (@mire) commented on DS-970:
----------------------------------------
This ticket still seems actual and well described. Marking as volunteer needed.
> Item Edit View, Edit Collection View, Control Panel need Navigation Improved
> for extensibility and DSpace needs a "SiteMap" page.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DS-970
> URL: https://jira.duraspace.org/browse/DS-970
> Project: DSpace
> Issue Type: Improvement
> Components: XMLUI
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1,
> 1.7.2
> Reporter: Mark Diggory
>
> Item Edit View, Edit Collection View, Control Panel need Navigation Improved
> for extensibility and DSpace needs a "SiteMap" page that will show all User
> and Administrative Options.
> These views require all pages to duplicate navigation tab options in their
> design. It'd be good not to have all this wired into one view, I'm not a
> big fan of the edit Item view, control panel view nor the edit collection
> views because they are not designed to be extensible. Thus I never implement
> features that "add to them" I always implement new pages to support a feature
> separately. This way, I do not need to add new navigation elements to "every
> single" page that would be part of that control panel, item edit view, etc.
> (Which is what had to happen recently with Curation Tools) It would be best
> if we could cleanup the design in this area, for instance, if we instead were
> to have the separate pages as "Options" listed under the Control Panel, they
> could be used to calculate navigation tabs in the Control Panel page rather
> than each page having to need to have the navigation hardwired within it.
> This could be adding a Transformer that is executed prior to any of the
> Controller Pages that would render the tab list in the body rather than
> placing that responsibility in the page. This would make that sort of
> extensibility much much simpler.
> Likewise, we could use such a full list of options to generate a complete
> "SiteMap" page for administering DSpace that included all sections and
> subsections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
