uidaholib / collectionbuilder-cdm-template Goto Github PK

auto generate from .json make variable with theme.yml

@dcnb @owikle do we want the credits.md "technical" info box on every about page?
The updates pulled in the version from CB-CDM, which isn't exactly correct for this situation. But also not sure we really want it on every about page--seems like having it described on Digital home is enough?

add to breadcrumbs, check on mobile

stuff like www.lib.uidaho.edu/digital/assets/images/

should be in www.lib.uidaho.edu/media/ or www.lib.uidaho.edu/digital/objects/

auto gen one?

@evanwill I tried to update my forked repo with your latest commits but accidentally ended up merging my changes to this branch. I'm getting confused with the revert process. Can you help? Sorry!

currently the item page has the "Rights" box which is not configurable.
It is automatically added if an item has a field named "rights" and/or "rightsstatement".

Looking at collections, a lot of metadata has these fields named random other things, including many recently done use "rights (standardized)", so rights box doesn't show up. Also, many config-metadata contain both the rights fields, so the item page displays the rights fields, then also includes the rights box.

Do we want to normalize this better? Just have one or the other? Make sure everyone actually changes the field names, and doesn't add them to config-metadata?

#home-title-box padding on mobile should be based on theme.home-title-y-padding some how, since it is currently hard coded as 5em.

maybe like theme.home-title-y-padding - 2em or /1.5 or something?
https://help.shopify.com/en/themes/liquid/filters/math-filters

just need to ensure we don't end up setting it to zero/negative if the original is small.

use text utility like text-wrap or text-truncate?
https://getbootstrap.com/docs/4.2/utilities/text/

unfortunately realized that this practice makes it hard working with fields in javascript...

accessibility issue, tooltips should only be on focusable elements,
https://getbootstrap.com/docs/4.3/components/tooltips/#markup

wrong on timeline where tooltip is on img

are the tooltips necessary, useful, best way to add information?
they are inaccessible on mobile also

Ready for review and move to web server (from Michelle):

• psychiana
• Potlatch Lumber Company (plcphotos)
• Columbia River Basin Project (crbproj)

• Adjust padding on index image when small screen

• Make nav sticky to bottom

timeline

Hi,
When I go into a collection in Collection Builder, and I go into the Browse tab, the images are not in numeric order based on Identification Number. Is it possible to add an option to view the images in order based on their Identification Numbers? I understand the randomness can help showcase different facets of the collection and that's fine, but it would also be nice to have an option to view the images in their correct arrangement (a.k.a. the arrangement that reflects their physical arrangement in our physical collections).

Thank you!! - Michelle Shannon

• handle hidden text in search (see sandborn)
• as javascript
• add gallery option

currently _include/feature/item-figure.html is compatible with an item that has an objectid, and is either an image or youtubeid.

Should it support PDF items as well?

Do we need a non-item figure include, for an image that isn't an object? Just pass it a link for image?

• stop using onload
• self enclosed functions
• move to lazyload.js v2 and only call when necessary, https://appelsiini.net/projects/lazyload/

• load geojson as separate step
• simplify CSS loading by combining files
• (?) filter buttons, https://github.com/maydemirx/leaflet-tag-filter-button
• (?) replace unfreeze with https://github.com/ghybs/Leaflet.MarkerCluster.LayerSupport

re: PR #16

use standard bootstrap button classes and override colors, rather than create new ones, to make style more themeable

most popular, active: https://github.com/aFarkas/lazysizes

add to subjects-js to filter out terms that are useless to the collection

is this worth while?

link to contact page or a qualtrics form?

@dcnb I created a branch cccidaho fresh from master and put all cccidaho stuff in and config-ed like the previous build.

• set up map cluster with no search
• swapped out the lazyload library for higher performance one (on browse only so far)
• I replaced browse with the working draft version of js-based-browse. works pretty good, still needs a bit of tweaks in the card, and could be optimized a bit more i think.

takes FOR EVER to build...

I found this out working on barstock branch. the buttons would put out links that ended "# basketball" and then searched for " basketball"

I fixed this in the branch by adding a trim to the btn for loop here:

for (var i = 0, len = btns.length; i < len; i++) {
if(btns[i] != "") {
card += '' + btns[i].trim() + '';
}

but I'll let @evanwill decide if that works

provide summary, instruction/ orientation to how to use the site.
= accessibility/usability guideline.

subject "accesss road"

@mshannon95 noticed issues with reflow not happening on Chrome when images lazyload on an about page item-figure include (works in Firefox, and may have worked fine until recently in Chrome).
This suggests need to add placeholder images (which we tried in past, but didn't love). This CCS-Tricks article suggested an inline svg option--that seems to work really well!

Add:
src="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 3 2'%3E%3C/svg%3E"
to images with data-src which are going to be lazy loaded.

I need to test on huge collections, but probably add to:

• timeline
• browsejs

var placeholder = "data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 3 2'%3E%3C/svg%3E"

use format field instead of Type in layouts to decide download, image, etc

• make if statements so unnecessary data downloads don't show up

• Is there a time-centric data format?

comments from people looking at recently built collections:

• they didn't get the all-collections button nav on digital logo,
• they were looking for ui library branding, and link back to library (it is only in footer)

maybe a top bar or update look of the all-collections nav button?

this potentially makes the api calls more portable to other systems...

• https://www.oclc.org/support/services/contentdm/help/customizing-website-help/other-customizations/iiif-api-support.en.html
• https://help.oclc.org/Metadata_Services/CONTENTdm/Advanced_website_customization/API_Reference/IIIF_API
• https://iiif.io/api/image/2.1/#uri-syntax

IIIF standard looks like:
{scheme}://{server}{/prefix}/{identifier}/{region}/{size}/{rotation}/{quality}.{format}

Which looks like this in CDM:
https://cdm17254.contentdm.oclc.org/digital/iiif/psychiana/548/full/pct:50/0/default.jpg

Get max size:
https://cdm17254.contentdm.oclc.org/digital/iiif/psychiana/548/full/max/0/default.jpg

Get image info example: https://cdm17254.contentdm.oclc.org/digital/iiif/psychiana/548/info.json

using js was hack for GH version, with find unique plugin it isn't necessary, would make big clouds much faster for users.

quotes in CSV text fields are escaped by using double quotes "", these don't get fixed by jekyll during page gen. replace with ' or pretty quotes in csvs?

add from Queered branch

• all-collections-nav-php @owikle
• google-analytics-php @evanwill

I'm not sure if this is necessary, but for some collections, we definitely more unique metadata searchable via the browse page. How should we set that up?

@owikle @dcnb major overhaul to match cdm-template to CB-CDM is in branch update-from-cdm

I am not sure how difficult it is going to be to migrate...
Here are some notes about migrating existing stuff:

metadata needs updated required fields:

• object-id > objectid
• youtube-id > youtubeid
• cdm-id > cdmid

Configuration migration might be a bit complicated details:

• theme and config have some updated options, many like "organization branding" that are the same for every collection.
• collection and site settings sections moved from theme to _config.yml
• old files were named x-config, I didn't delete them from the branch, but added the new config-x, with updated fields/names. the old config content will have to be migrated to the new style
• config-browse was already in project but has updated fields/names, so might need updates

Includes:

• old "item-figure.html" works, but might be better moving the include to the newer version "feature/item-figure.html"

Color theme-ing:

• the custom.css was full of random junk which is now all cleaned up. advanced options set in theme.yml will now work.
• _sass/_colors.scss is no longer used, instead _data/config-theme-colors.csv generates the custom UI brand color elements. (currently only pride-gold and clearwater are used anywhere. if we aren't going to use any others, we should remove them to save on css)
• however, the custom color btns aren't used, instead it is currently overriding bootstrap colors with theme colors using config-theme-colors. The btns in the project that used to have custom classes are just -primary (pride-gold) and -info (clearwater), so it made sense to just leave it same as CB-CDM this way.

Subject cloud, old version had some differences from CB-CDM, which I removed for now:

• cloud box styling, old class="text-center my-4 bg-dark", new class="text-center my-4 bg-light border rounded p-2"
• btn sizing: old had size ranging from 0.8em to 3.6em (.tagcloud0 to .tagcloud10), new range is 0.4em to 3.0em. I think the larger size was to compensate for size of Ringside? If you think it should be made bigger again, probably copy the sizing from _sass/_pages.scss into _custom.scss to override it.

Design questions:

• I don't think the custom btns (clearwater + gold) have enough contrast (they fail accessibility test)
• what about a darker nav-bar and footer? try just adding dark,#191919 in config-color-theme