Interesting question! A few examples from XMLUI repositories that we were
involved in:

*Belspo / ORFEO*

For this repository, we had to marry the identity of a centralised
repository, with the identity of different independent scientific research
institutions.

Participating institutions had the choice to stick with the generic
repository branding, or provide specification limited to:
- background colours
- community homepage imagery

Homepage: https://orfeo.kbr.be/
Community page with its own background colours:
https://orfeo.kbr.be/handle/internal/10

The usecase of a user starting a search from the homepage, and potentially
landing on items from different collections/communities was an important
one, and the client felt that the differences could not be too drastic, so
the user didn't feel that each item page felt like it was part of a totally
different website.

The possibility of an institution to match the background colours of their
site, had the benefit that when users would be jumping from the
institutional website, to the specific community, the break in look & feel
would also be less big.

*iPubli / INSERM*

The community/collection tree of this repository is organized along types
of content. The three top level community have their own colours to make it
clear to the user which type of content is being visited.

Homepage: http://www.ipubli.inserm.fr/

TLC pages:
http://www.ipubli.inserm.fr/handle/10608/6819
http://www.ipubli.inserm.fr/handle/10608/1
http://www.ipubli.inserm.fr/handle/10608/224

best regards,

Bram


[image: logo] Bram Luyten
*250-B Luci*us Gordon Drive, Suite 3A, West Henrietta, NY 14586
Gaston Geenslaan 14, 3001 Leuven, Belgium
atmire.com
<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>


On Fri, 2 Aug 2019 at 18:38, Terry Brady <[email protected]> wrote:

> We support a variety of community and collection level themes in our
> repository (using XMLUI).
>
> We customize the following.
>
>    - Landing page: logo, link, some CSS, footer links
>    - Item display page - which fields appear
>    - Custom facets per collection
>
> Here are some links that illustrate the differences.
>
>    - https://repository.library.georgetown.edu/handle/10822/1
>    - https://repository.library.georgetown.edu/handle/10822/555527
>    - Law center theme
>    - https://repository.library.georgetown.edu/handle/10822/761426
>       - Law collection with custom display, sort, and facets plus a
>       glossary link.
>       - This collection supports formatted markdown on item pages.
>    - https://repository.library.georgetown.edu/handle/10822/761365
>    - Art collection with custom item page and facets
>    - https://repository.library.georgetown.edu/handle/10822/549457
>       - Video collection with custom themes.
>
> We have 4 primary themes: IR, Special Collections, Law Center, Bioethics.
>
> Within each of those themes, we have custom code to evaluate the owning
> community/collection to trigger lower level customizations.
>
> Here is a presentation that we gave in 2017 on our theme approach:
> https://gitpitch.com/terrywbrady/dspaceUserMeeting?p=customizedCollections#/
>
> Terry
>
> On Fri, Aug 2, 2019 at 9:18 AM Gail Steinhart <[email protected]> wrote:
>
>> Hi all,
>>
>>
>>
>> We anticipate integrating some college-level repositories into our
>> existing DSpace instance (6.3), and supporting some level of branding for
>> each that is distinct from our current theme. I’m aware of the University
>> of Minnesota supporting slightly different theme for its data repository
>> and for satellite campuses. Are there any other examples out there that
>> people can share? Please send along the URLs if you have examples.
>>
>>
>>
>> Thanks so much,
>>
>> Gail
>>
>>
>>
>> Gail Steinhart
>>
>> Scholarly Communication Librarian
>>
>> Cornell University Library
>>
>> 218 Olin Library | 607.255.7251
>>
>> *https://orcid.org/0000-0002-2441-1651
>> <https://orcid.org/0000-0002-2441-1651>* | @gailst
>> <https://twitter.com/gailst>
>>
>> she/hers
>>
>>
>>
>> --
>> All messages to this mailing list should adhere to the DuraSpace Code of
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-community/F067521F-3CCB-43D3-A1AB-6A593AD18954%40cornell.edu
>> <https://groups.google.com/d/msgid/dspace-community/F067521F-3CCB-43D3-A1AB-6A593AD18954%40cornell.edu?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://github.com/terrywbrady/info
> 425-298-5498 (Seattle, WA)
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-community/CAMp2YEz6RRLZ_vQhOLNpJp7bx8j6Db_qTrtGMmqsQF3-byKgaw%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-community/CAMp2YEz6RRLZ_vQhOLNpJp7bx8j6Db_qTrtGMmqsQF3-byKgaw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/CACwo3X0vOvc-k4DRGeaSRQqUNH08ivvCdJMz%2Ba3NgkLUrFqJwg%40mail.gmail.com.

Reply via email to