Wowsers. I had completely missed the community/collection part of that theme manager. I'm a little less than happy with that solution to our issue, because we don't really want a new look/feel, but simply an alternate simple item display. It would mean that any change in the theme itself would need to be replicated in the additional theme.
It might be worth the extra effort, though, as I found out yesterday that our new schema isn't being indexed; I still have to look into it to see if I can get those fields into the index. B-- >>> On 6/7/2011 at 1:10 AM, in message <[email protected]>, Saqib Ilyas <[email protected]> wrote: > A little bit of investigation shows that you might do this by creating a new > theme and modifying xmlui.xconf by setting the handle attribute in the > <theme> tag to select a theme for a particular collection. I hope that I am > on the right track. I'll go ahead and play with this and report my findings > later. > > On Tue, Jun 7, 2011 at 10:07 AM, Saqib Ilyas <[email protected]> wrote: > >> Thanks Brian. The document > here<http://www.google.com.pk/url?sa=t&source=web&cd=2&ved=0CCkQFjAB&url=http%3 > > A%2F%2Fwww.dspace.cam.ac.uk%2Fbitstream%2F1810%2F213741%2F1%2FPhillips.ppt&ei= > Na_tTc3TCMes8gPJ0rCXBw&usg=AFQjCNGx-acAJcoT_l3GTmRHinw52ITGjQ>says that XMLUI > "Enables >> communities and collections to customize their interface." I need to go read >> the documentation but the way you've suggested, is that exactly how XMLUI >> does it or perhaps based on the claim of the document I cited, there is >> perhaps another way, too? >> >> >> On Mon, Jun 6, 2011 at 8:07 PM, Brian Freels-Stendel <[email protected]>wrote: >> >>> Hi there, >>> >>> My understanding is that you are correct, XMLUI does not allow different >>> displays on a collection level. >>> >>> However, we just went through this same situation, and came up with a >>> nasty hack. >>> >>> In our theme's copy of template.xsl, we tested for the existence of the >>> new schema, which we named "data": >>> >>> <!-- Generate the info about the item from the metadata section --> >>> <xsl:template match="dim:dim" mode="itemSummaryView-DIM"> >>> <table class="ds-includeSet-table"> >>> <xsl:choose> >>> <xsl:when test="dim:field[@mdschema='data']"> >>> <xsl:call-template >>> name="itemSummaryView-DIM-fields-DATA-mdschema"> >>> </xsl:call-template> >>> </xsl:when> >>> <xsl:otherwise> >>> <xsl:call-template name="itemSummaryView-DIM-fields"> >>> </xsl:call-template> >>> </xsl:otherwise> >>> </xsl:choose> >>> </table> >>> </xsl:template> >>> >>> Then, we created a copy of the "itemSummaryView-DIM-fields" template and >>> modified it to display the alternate view. >>> >>> B-- >>> >>> >>> On 6/5/2011 at 11:32 PM, in message >>> <[email protected]>, Saqib Ilyas >>> <[email protected]> wrote: >>> > Hello >>> > For one of the collections on our library's DSpace installation, we need >>> a >>> > customized schema. For all other collections, Dublin Core is just fine. >>> I >>> > have created a new schema and bulk imported items. Is it possible to >>> have a >>> > different item layout displayed when a user clicks on an item in this >>> > collection (while the default is followed for items in other >>> collections)? >>> > For instance, a different set of fields is displayed. >>> >>From what I could gather through web searched, it seems that whatever I >>> > change in the CSS, would be global. Am I right? >>> > Thanks and best regards >>> >>> >> >> >> -- >> Muhammad Saqib Ilyas >> PhD Student, Computer Science and Engineering >> Lahore University of Management Sciences >> > ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
