RC Logbook

• allows authors to define both a graphical 2d layout and a responsive version of the same page content
• the responsive version of an exposition is the same as text based, now understood as a linear ordering of tools
• mixing the two formats within one exposition
• fascilitate migrate pages between the two formats
• the author decides which layouts are available to the reader

how to make it easier within education to track an exposition and prevent students from making new ones?

that are somehow linked (show that something is just a newer version of an older exposition)

Portal admins can view how many "expositions in progress" there are, see who is editing something.

instead of forbidding deletion of media used as preview/background, ask the user for permission to delete it and automatically deselect/delink. If no background image is selected, it should either display the generated thumb or the background color in style.

Inform user on DOI being created, and that this means that the reference is permanent.

(upload/add but not change) in media repo

(currently, uses pretty low bitrate, filters out everything above 15k)

current lack of limits stimulates risky designs

save vs. submit, inform/warn people when deadline is close, message on save that this is not submitting

1. The main language of an exposition should be displayed in the metadata page.
2. The abstract displayed in the Navigation bar abstract box should be the same as the language of the exposition, and there should be a dropdown to switch between languages (if translations are available).

more fail safe: big expositions cause timeouts, like https://www.researchcatalogue.net/view/568007/568008

zencoder: When uploading a video format that is not supported, show user hint what would work.

for users within portal user list (for organising)

to separate it from keywords, archive organisation, similar to current reviewing tags.

of expositions and media repo

(clean up old state first)

command within editors (instead of copy paste tools)

to media repo set

button in collaboration message dialog

removed from messages, should be prompt or notification. State should be live from the current state

When dragging from simple media: should use tool default instead of intrensic size

(automatic detection)

finding the right person if you only have an email.

to articles on the frontpage, published by JAR for example.

when FEIDE student has logged in first time, creating a new account

Reproduce? in text-based editor, not always translated to live url (https://www.researchcatalogue.net/text-editor/simple-media-resource?research=547070&simple-media=945677)

from "in revision" -> "in review" (currenlty only happens when the author does it)

for comments on pages that can be seen by the commenter.

exposition: https://www.researchcatalogue.net/view/462390/462391 author: Mariella Greil-Moebius https://www.researchcatalogue.net/profile/?person=91218

https://www.researchcatalogue.net/editor?research=861875&weave=944937

• this is an alternative form of publication where it is fixed, but only visible to portal admins.
• probably needs some extra meta-data like department / context in which the archived exposition was produced.

#container-weave .tool-text { -webkit-text-size-adjust: none; -moz-text-size-adjust: none; -ms-text-size-adjust: none; }

#container-weave .tool-simpletext { -webkit-text-size-adjust: none; -moz-text-size-adjust: none; -ms-text-size-adjust: none; }

We would like to reduce the "font warning" messages, by making sure only fonts are used that RC can host itself. Currently, many of our fonts (Verdana, Terminal), are not available everywhere, and we cannot host them either as far as I understand? This is what Microsoft say about it: https://docs.microsoft.com/en-us/typography/fonts/font-faq#redistribution-and-extended-rights Correct font is kind of important, and authors are often not aware that the wrong font may be displayed for many of their readers.

The solution we have in mind consists of 3 parts:

1. Add self-hosted fonts:

We have selected a list of public domain fonts, which the RC can self-host, some of them are metrically based on Arial/Helvetica. These fonts should be added to the HTML/text font dropdown and the .woff served with every exposition:

Sans Serif:

• Nimbus Sans L (https://www.fontsquirrel.com/fonts/nimbus-sans-l)
• Arimo (https://fonts.google.com/specimen/Arimo)
• Lato (GF) (https://fonts.google.com/specimen/Lato)
• Roboto (GF) (https://fonts.google.com/specimen/Roboto)
• PT Sans (https://fonts.google.com/specimen/PT+Sans?query=pt+sans)
• Open Sans (https://fonts.google.com/specimen/Open+Sans?query=open+sans)

Serif:

• Libre Baskerville (https://fonts.google.com/specimen/Libre+Baskerville?query=Libre+basker)
• Merriweather (GF) (https://fonts.google.com/specimen/Merriweather?query=Merriweather)

Mono:

• Roboto Mono (GF) https://fonts.google.com/specimen/Roboto+Mono?query=roboto+mono
• Courier Prime https://www.fontsquirrel.com/fonts/courier-prime?q[term]=courier&q[search_check]=Y

1. User added fonts:

In the expositions settings (edit metadata, edit research dialog) we would like to add a "Fonts" tab, where the user can can upload (multiple) fonts (.woff or .ttf). There should also be a required name field, under which they will appear in the font dropdown of HTML and text tools. These fonts are local to the exposition and served by RC when the exposition is viewed. We should add a warning that the user is responsible for checking that the license of the font allows using it.

For new expositions, only make available the self-hosted and the user-uploaded fonts. For all older expositions, authors should still be able to use the old fonts (so both the old and new fonts). This includes expositions that have been restored from an old snapshot.

Does this solution make sense to you as well, is it possible?