Right, but you should consider 3) as an enhancement of 2) because you
will also need to store the handles in project item's metadata. Also
2) is less difficult to implement and you can fluently work from there
to implement 3).

You didn't specify which interface and theme you intend to use so I'll
assume XMLUI and Mirage.

As for documentation, these are the standard primers:
https://wiki.duraspace.org/display/DSPACE/Manakin+theme+tutorial
https://wiki.duraspace.org/display/DSPACE/Manakin+Themes

Specifically for your needs, you will want to work with  the summary
view templates in
[dspace]/webapps/xmlui/themes/Mirage/lib/xsl/aspect/artifactbrowser/item-view.xsl
(that's Mirage in 1.8.0)

I recommend that you work in the deployed webapp in [dspace]. That way
you don't need to redeploy the webapp after you change an .xsl file,
you'll just reload the page in your browser. Of course, don't forget
to copy your new theme before you redepoy DSspace in the future (when
upgrading etc).

Regards,
~~helix84

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to