Skip to content

Latest commit

 

History

History
95 lines (64 loc) · 4.34 KB

README.md

File metadata and controls

95 lines (64 loc) · 4.34 KB

UC Berkeley Library Dataverse assets

These are files used to customize the UC Berkeley Library Dataverse's user interface elements. Other than changes made in the Dataverse admin UI (e.g. names of Dataverse collections), these fall into two primary buckets: branding and styling changes, and changes to locale files.

Branding changes

See Dataverse's "Branding Your Installation" documentation.

Logos

Custom Homepage

Custom footer

TODO: this could go in /home/dataverse instead

Custom stylesheet

TODO: this could go in /home/dataverse instead

Google Analytics snippet (production only)

TODO: this could go in /home/dataverse instead

Add terms of use

TODO: this could go in /home/dataverse instead

Add custom home page

TODO: this could go in /home/dataverse instead

Adding “About” to the nav bar

Changing user guide navbar link to point to Terms of Use

Add text to copyright

Locale files

Many display strings are managed in the Dataverse's locale files. See upstream Internationalization documentation.

Likely deployment path

Presuming that this repo is checked out or accessible from /home/dataverse/dataverse-assets:

  • Run ./asadmin create-jvm-options '-Ddataverse.lang.directory=/home/dataverse/dataverse-assets/langBundles'
  • Restart Dataverse

Manual process

Updating locale files from upstream

This should only be necessary when you upgrade Dataverse.

  • Run git clone https://github.com/iqss/dataverse
  • Run git checkout v6.3 (or whatever the appropriate tag is for your version)
  • Run cd
  • Run cp dataverse/src/main/propertyFiles/* langBundles
  • Run cd langBundles
  • Run git apply ../locale.patch
  • Review any differences, confirm they're correct
  • Commit your changes

Occasionally, you may need to create a new patch file.