[Archivesspace_Users_Group] Customizing ArchivesSpaceTemplates Based on Repository
mark.custer at yale.edu
Wed Jan 6 13:31:35 EST 2016
I’m not sure if there are already examples in the wild that do this (if you do a Google search for “archivesspace public interface” various live sites will show up, though, since that phrase is used by default in the HTML header), but once the next iteration of the ASpace PUI is released, it’ll contain repository information at the collection level. A release date hasn’t been scheduled for the PUI redesign release, but hopefully there will be more information to share about that in the next few months.
Early wireframes and static screen shots of the design mockups are available here: http://cherryhill.github.io/aspace_pui/index.html
Just an FYI, depending on when you plan to use the ArchivesSpace Public User Interface.
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Terry Brady
Sent: Wednesday, January 06, 2016 12:11 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Customizing ArchivesSpaceTemplates Based on Repository
We are interested in customizing our public-facing ArchivesSpace templates based on the repository containing a resource.
We would like to provide a custom logo for each repository and we would like to alter some contact language as a user navigates between resources in different repositories.
Does such a mechanism already exist? If so, how do I make use of that mechanism?
We see that the URL often identifies the containing repository id. It would be useful if some of the containing divs contained the repository id in their markup.
Applications Programmer Analyst
Georgetown University Library Information Technology
425-298-5498 (Seattle, WA)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group