1

(2 replies, posted in Questions on Using the RC)

Sorry, I think your question was overlooked when it was originally asked.
It is not possible to merge expositions, and I don't think it will be supported soon, as it would break some nice properties of expositions (for example, that pages links never change). However, you can use normal hyperlinks (https://guide.researchcatalogue.net/#hyperlinking) to create navigation paths for your readers between the two: if you do it well, the reader probably wouldn't even notice that there are two expositions. Also, in the table of contents, it is possible to supply (instead of selecting an internal page) an HTML hyperlink <a href="url"></a>. Using this method, it allows you to put "external" links in the TOC, for example to pages which are not part of another exposition. If you are not familiar with HTML's <a href=""> you may find this useful: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a

2

(2 replies, posted in Questions on Using the RC)

Hello Tijs,

Pseudonym can be used to change your usual name to another, however, it does not anonymize (!) an exposition in a double blind kind of way, as the name will still be visible in metadata. It's function is for publishing for a group or something that you are not really the author of, but not really to be anonymous.

There are alternatives though:
1. It is possible to have an anonymous account where we apply an alias instead of your real name,
but this has to be arranged with support@researchcatalogue.net, you will need to provide an alternative email address if you do not want your real name account use this alias as well.
2. It is possible to have a double-blind review in a portal review workflow.

Note that copyright fields will not be hidden if used and that SAR admins will always be (and need to be) able to see the real author because in case of copyright troubles, we need to be able to identify the "real" author.

Best,
Casper Schipper

Dear Timo,

Sorry for taking a long time to respond. Indeed, RAW CSS only applies to the page, not to footnotes within it.
This is because the footnotes in RC are loaded currently as separate pages: they are basically mini-expositions in an iframe.

Given your problem, I guess it would make sense to duplicate whatever style was in the page in any footnote there, however, there is some technical challange there, as footnotes can migrate between pages and RAW CSS is local to the page.

I think a better long-term solution would be to have a global stylesheet that applies to all content in one exposition, including footnotes. I find that in using RAW CSS myself, I tend to copy a lot of CSS back and forth between pages, and there is not really a need to have different CSS between pages, as it can be easily localized to a page id if needed. However, because of backwards compatibility, we will have to think a little bit how to implement this clearly.
I will discuss and be back to you.

4

(1 replies, posted in Feature Requests)

Thank you! I think that sounds like a very reasonable suggestion. We are going to try to see what we can do in this regard. I think it would be a step forward in general accessibility as well.

In a similar spirit, me and Daniele Pozzi have been working on general RC exposition parser, one of the things we imagined it could be used for is to create better text versions. We already support downloading the exposition content (tools, media-urls, text, style, position) as a JSON. You can find a link at the bottom of an exposition detail page within the RC Visual Map link, for example here. It shouldn't be very hard for us to add a reader-friendly output as well.

5

(1 replies, posted in Feature Requests)

Thank you! Shouldn't be too difficult to implement.
I have put it on our list and will let you know if we can do it.

Best,
Casper

6

(1 replies, posted in Questions on Using the RC)

Hi Tijs,

These filesizes may be problematic and is over what we usually expect in RC. However, I think the first important question is: are you planning to use these in an exposition or display them just as a public set?

If you are using them in an exposition, at this point in time, there is not much point in uploading large video files into the RC, since all videos are transcoded in expositions to a much smaller size anyway, to save bandwidth. Since transcoding is quite a large cost for the RC, we currently only transcode to a single quality instead of providing different options for different bandwidths, although we are considering more flexible options in the future (for example, allowing people to do their own transcoding), since the current standard is not always sufficient for all research purposes.

The media repository does keep the originals and you can always download them as such later but comes with the implicit understanding for providing "unlimited" space is that you will use uploaded materials in an exposition at some point (we understand that this may take a long time).

7

(1 replies, posted in Bug Reports)

Can you share an example with me ( you can also send it directly to casper@researchcatalogue.net) ?

8

(2 replies, posted in General Discussion)

It has been corrected now. Thanks again for notifying us!

9

(2 replies, posted in General Discussion)

Hi Hanns,

Thank you for noticing this: this change was actually unintentional. The default should have been "all reserved" (for media files). There could be some arguments for making it CC-BY-NC-SA, but I think it is slightly safer to have "all rights reserved", since as far as I understand copyright, that is implied anyhow when no license is included. It logically makes more sense. I will have it changed back immediately.

If an exposition only consists of a video that needs to be full screen, with maybe some text below it, the easiest option is to make a "text-based" exposition and use the "full width video template". The limitation of that option is that a text-based page cannot be combined in a larger exposition with graphical or block pages.

So if you want to have a full screen video in a graphical exposition, do the following:
- Create a block page
- Add the video in a single row
You can make the rows fill the complete width of the screen by adding the following CSS lines to raw CSS in page's style settings.

/* RAW CSS */

#content .row {
  border: 0;
  width: 100vw;
  position: relative;
  left: 50%;
  right: 50%;
  margin-left: -50vw;
  margin-right: -50vw;
}

.cell {
   padding:0;
}

/* end of RAW CSS */

if you want this width for only a single row, you will need to use the browser inspector to find the correct identifier. You can also send the link of the exposition to me (casper@researchcatalogue.net) if you need help with this.

Reducing the size of the tools will help, but resizing them before uploading will not help much. The RC rescales images so they are optimized for the size in which they appear in your exposition. The important thing is that this works both ways, so if you upload a low resolution image, but stretch the tool up to a large size in your exposition, it will still be big in size. Otherwise it may be necessary to break things up in separate pages.

We have had experimental expositions before that were pushing the limits, for example: https://www.researchcatalogue.net/view/1283942/1354509. This exposition does not load on all computers, but given the experimental nature of the exposition, this was chosen to be a feature of it (by the journal editors and the authors). I think this is the trade-off you have to make: do you keep to the concept but accept that some people may not be able to view it, or do you compromise a bit so to enlarge the audience. Another option could be to make different variants, "light version"/"heavy version".

Pages cannot be duplicated directly, instead:
select all tools on the original page (ctrl/cmd + a), copy them (ctrl/cmd + c)
create a new empty page, and paste: ctrl/cmd + v
is the quickest alternative.

This works only for the graphical editor, since if you do this on a block page, it pastes all tools in the one column.
A duplication function would make sense, so I have added it on our list of ideas, but it may take some time to materialize.

Hi,

As far as I know, there is no direct way to access an exposition and login simultaneously.

The way that I solved this, is to login first using wget or curl. You store the session cookie locally and reuse it for subsequent requests. Of course you will need to fetch this cookie again after some time, since RC sessions are not infinite.

The link for logging in to the RC is:
https://www.researchcatalogue.net/session/login

You provide username and password as url-encoded values. (?username=myusername&password=mypassword)

here's a snippet of ocaml code:

let login_cmd () =
  let credentials_form_data =
    [ "username="; Secret.username; "&password="; Secret.password ]
    |> String.concat ""
  in
  let args =
    [|
      "wget";
      "-v";
      "--keep-session-cookies";
      "--save-cookies";
      "cookies.txt";
      "-O";
      "-";
      "--post-data=" ^ credentials_form_data;
      login_url;
    |]
  in

  let inp = Unix.open_process_args_in "wget" args in
  (* let _ = print_endline cmd in *)
  read_lines inp |> String.concat "\n"

However, I'd say your share link method has some advantages as well, in that you don't have to hardcode your credentials into code.

Thanks for noticing! I cannot seem to reproduce the issue here. One explanation may be that it was a temporary side-effect of the recent resolution upgrade of the RC (and an outdated link to the logo persisting in the browser cache).
Can you try again and let us know?

(...regarding sharing images in this board: currently, this is not possible. I will see if it is possible to enable this)

Most likely this is because you have another tab/browser with the exposition open: the blue border means that the tool is selected in another tab. The RC allows you to collaborate on expositions in real time, if you are collaborating with other users, the blue border allows you to see what the other user is working on.

16

(4 replies, posted in Bug Reports)

Thanks! One thing that jumps to my mind that you could try is to set the default color of hyperlinks in the page settings. You can reach these by going to the right hand tab > pages and open the "edit page" dialog through clicking the icon that looks like a pencil.
edit link color

17

(4 replies, posted in Bug Reports)

We have not seen this issue before, thank you for notifying us!
For us to inspect what is going wrong, can you send us the tool content (just click HTML button in HTML tool).
or mail us the link of the exposition page (casper@researchcatalogue.net)

best,
Casper

Polifonia projects consists mainly of data once imported from an external source to make them searchable through the RC. It was also possible to create them "by hand", but this feature was not used a lot, and actually confused a lot of users, so we disabled it.

The current way to group expositions is to use the Group feature. A group can be created by portal admins.
A group (https://guide.researchcatalogue.net/#groups) contains both users (members) and expositions, but also has its own group  page with a description, title and status (similar to a project) and the list of expositions that are part of it. This group "profile" page is editable by the group admin. Once an exposition is connected to a group by the admin, the exposition will also mention the group on its own Metadata page: so, the link between Group and exposition is bidirectional.

So I think what you need is a Group, is the project you would like to create an overview for happening within one of the portal partners?

19

(1 replies, posted in Feature Requests)

Thank you! I have noted this down as a feature adjustment.

There is a workaround directly embedding into an HTML tool, but I suspect this is not really the answer to your particular problem, since you would still need to manually retrieve the <embed> code from each video. It would be easier if the embed tools can be just copied, of course.

20

(2 replies, posted in Questions on Using the RC)

Thank you for reporting this problem: the font migration feature is not available for newer expositions, it was created to solve an issue with older expositions. But from your example I can see how a similar feature would be very useful solving font issues.
I will try to see if we can provide this, but may take some time.

I have posted a little tool here to find all unsupported use of fonts in an exposition:
https://github.com/casperschipper/font_ … /README.md
It is a little finicky, you have to paste a bunch of stuff in browser console, but it makes it easy to find all problems causing fonts.

Hello Flick,

the export has been adjusted, so expositions can now also be hosted on your own domain.
In my tests it works as expected now, can you try and let us know?

22

(3 replies, posted in Questions on Using the RC)

Yes, the bug that caused the problem was resolved yesterday. Thanks for hanging in there!

23

(3 replies, posted in Questions on Using the RC)

Dear Lenka,

We encountered this problem this morning as well, it actually affects all footnotes.
The bug has been reported, I expect it to be caused by just a minor error, so my hope is it can be resolved rather soon.
Sorry for the inconvenience!

Hello Flick,

Thank you for your information about this problem, very helpful!
I have reported the issue with the developers.

The cause of the issue: it appears that RC expositions determine their location (in javascript) by doing a check "window.location.protocol"===":file" and similar. If this test returns negative, the exposition assumes it is running from inside the RC and this causes wrong paths for media files and footnotes/popovers, hence you see the 404's. It can be fixed by hand if you are in a hurry, but better to wait for this to be fixed in the export itself. I will keep you posted!

25

(1 replies, posted in Feature Requests)

Up until now, discussion between portal admins was happening on the portal partner forum Basecamp forum (you are registered there as well).  https://sar-online.basecamphq.com/companies

There are certain drawbacks to using Basecamp, but one advantage is that you can easily choose who is notified of your posts.