phaidra / phaidra-ui Goto Github PK

Sort roles alphabetically, but keep the role 'other' first:

https://github.com/phaidra/phaidra-vue-components/blob/6ba6aac2264c9f09db60b6320d166623b533eb71/src/store/modules/vocabulary.js#L1216

Also when locale is changed, re-sort roles and orgunits via dispatched store action

all the mandatory fields should be shown when creating collection

Draft. TBD on Thursday.

We have multiple instances, and need a way to manage their configurations.

Instances

• e-book.fwf.ac.at [angular]
• phaidra.bibliothek.uni-ak.ac.at [old perl? thing]
• phaidra.cab.unipd.it [custom, angular-material, jquery]
• phaidra.fhstp.ac.at [old perl? thing]
• phaidra.kug.ac.at [angular]
• phaidra.ufg.at [old perl? thing]
• volare.vorarlberg.at [old perl? thing]

There are essentially two ways:

A) decide on the configuration at build time, baking it in with the build.

• requires building the software anew for each instance
• others' configs are not visible

B) ship all configurations with the build, pick the right one based on the value
of location.host (env "sniffing").

• one build for all
• everyone's configs are visible to all parties (open source)

Switching at runtime

Do we want to be able to switch configs at runtime? It seems like we do (e.g.
using the header dropdown on app01), at least on non-production instances (to
test styles, etc.).

Privacy

Are we (and other unis) comfortable having the configuration options saved in a open source repository?
It's not a problem to have private configs outside the repo.
They should still be able to make build with INSTANCE=foo, that would target their private config.

What's part of an instance config?

• api urls
• theme settings
• search facets
• logo url
• language (#11)

(which of these should be changeable dynamically?)

Search

Is a route target component, so passing props to it (dynamic ones) is not possible.

Settings Store

I think the vuex store is a perfectly adequate place for keeping the settings.
Comonents can react when accessing the settigns as they do now.
Alternatively we can use global 'settings' mixin as discussed before.

Solution

Best of both worlds.
Do separate builds per instance, bundling only the required config.
Config can keep the current style, with global settings, and switchable settings.
Use a tool like webpack's https://webpack.js.org/plugins/normal-module-replacement-plugin/
to make importing a config file be resolved based on an env var.
Build can then be called with INSTANCE=univie npm run build: webpack will
include config/univie.js when you write import config from 'APP_CONFIG'
App.vue will then place the config into the store, under settings, as it does now.
When these settings change, components like search can update reactively.
This means we will have no symlinks.

unknown-58f6510:0: Schemas validity error : Element '{http://phaidra.univie.ac.at/XML/metadata/lom/V1.0}contribute': This element is not expected. Expected is ( {http://phaidra.univie.ac.at/XML/metadata/extended/V1.0}metadataqualitycheck ).

Show EXIF metadata on detail object page?

Consider generating EXIF metadata on the fly upon user's request instead of ingesting it as a datastream. Any authorization needed? Caching needed?

on collection detail page, show the collection hierarchy, if there is any

eg col o:459006 is part of o:459021 and has o:459005 as member. So if I'm eg on detail object of o:459006 it should show:

• o:459021 - 650 Jahre Universität Wien
• • o:459006 - Ausstellung - Wien 1365. Eine Universität ensteht
• • • o:459005 - Wien 1365. Eine Universität entsteht - Fotos

it should show the whole hierarchy, not just parents (there could be more) and children, so it should traverse the ifpartof relation recursive in both ways (up and down)

Consider adding Open Graph and Twitter Card meta tags for better sharing of Phaidra webpages on social media.

Useful reference (albeit a bit old): https://css-tricks.com/essential-meta-tags-social-media/

HTML metadata manager for Vue.js: https://vue-meta.nuxtjs.org/

In the object's landing page, consider embedding the following in meta/link/script HTML tags to increase machine readability:

• Dublin Core metadata
• Schema.org metadata
• Typed links (see Signposting approach, in particular https://signposting.org/FAIR/)

Search engine discoverability would also benefit.

Example of embedding: see source code of https://phaidra.cab.unipd.it/o:453700.

ssia

please configure the pdf viewer so that it's no possible to open another pdf in it (remove "Open file")

<title>null (Phaidra - undefined)</title>

Polyfills

• Fetch https://github.com/github/fetch
• Promises https://github.com/taylorhakes/promise-polyfill

On the object's detail page of Phaidra classic UI, Picture objects have a link labelled as "Open in new window" below the embedded image viewer. The link points to a dedicated page, e.g. https://phaidra.univie.ac.at/imageserver/o:1202599.

The page and the link are currently missing in phaidra-ui.

On collection detail page, show collection members (pid, small thumbnail title). The view needs to be paged, because there can be thousands. Use SOLRs ispartof: field for this and pos_in_o_ to sort them (this is only defined in some collection).

you can input only a year, but then you get 1 January YYYY, you should get only YYYY.

• remove -hassuccessor:* when searching for collection members otherwise objects whose version isn't the latest won't be displayed in search results

• Show a label like "This object has a later version" in search results when an object has a later version. That could also be a link to the successor.

Pages like https://phaidra.univie.ac.at/imageserver/o:1202599 should come with a title and possibly a link to the object detail. Classic UI example page https://phaidra.cab.unipd.it/imageserver/o:15413.

https://github.com/kraih/mojo/wiki/Hypnotoad-prefork-web-server#database-connection-problem-in-preforking

i have to follow the instructions, otherwise i'm mostly getting 'MySQL server has gone away'

morbo works fine.

see eg https://github.com/phaidra/theke/blob/a4ca5fe9a6b373232bfb95e24717865673d5a922/src/components/Search.vue#L208

only add 'pid', 'dc_title', 'dc_creator' and 'bib_published' for now.