[CollEc] CollEc 2.0 Access

[Thomas Krichel]

  Düben, Christian writes

> Can you point test.collec.repec.org to http://95.216.35.87:8080?

  I think tihs is done. 

> I set up the user authentication to restrict access until the app is publicly released.

  I don't see much of a sense in doing that, but you are the boss here.

> Start up speed varies greatly between sessions. Sometimes the app
> starts almost immediately and sometimes it takes quite a while or
> even fails. ShinyProxy handles this stage and I am not sure why it
> is so volatile.

  I think over the post week I found that the machine was running
  very slow on certain time. I found disk space rising to 94%,
  causing me great concern. I don't know how to count what is
  in your part. I killed all backups that the machine had. As
  of lately disk space dropped considerably. 


> Many economists are not familiar with graph theory. And that is why the documentation explains the basics in a simply way. Edge weights are a key component of graphs and in my opinion one of the easiest parts to understand. Users do not have to be familiar with the slightly more complex shortest cost path algorithms or centrality measures to understand how edge weights work. If required, I can add another paragraph and a plot on edge weights to the documentation.
> 

  I think seeing a list of top-rated folk right at the start will
  prolly motivate users.

> Hosting the video on the server would indeed make the cookie
> notification obsolete. The motivation to embed a video hosted on
> Youtube comes from Youtube's video player. It automatically adjusts
> the resolution to the user's bandwidth, provides a rather stable
> performance, works well in different browsers and allows users to
> modify the speed.

  But then show you ads, right?

> Other video players used online tend to be more
> annoying to use. They get stuck, complain about missing browser
> plugins, do sometimes not adjust dynamically to bandwidth
> limitations and come with fewer customizable settings. I can add the
> video via the HTML video tag. And then we check how it performs in
> the web application called by different browsers. If that does not
> work as intended we can still try other players or host it on
> Youtube.

  I

> I embedded the video in the introduction rather than the
> documentation because of feedback I received on GraphEc. The feedback
> was that users should understand right at the start how the app works
> - without having to click through the other tabs. The video is like a
> paper's abstract. It is a brief, convenient, initial overview
> presented to the user without him or her going through the details,
> i.e. the documentation. And besides that everyone likes to watch
> videos. Some users might not find it as enjoyable as funny cat
> videos, but it still makes the app appear more active and engaging
> from the start.

  I hardly represent the averae user, so I can't comment on this. 

> You mention the year 2013 in your e-mail. Should I use that as the year you introduced CollEc?

  I'm sorry. No. I'm really bad at this. I think the first
  mention as a runnig service on RePEc-run is on 25 January 2011.

> I guess I somehow incorrectly understood CollEc to be a service from the early RePEc days.

  Can't be since RAS is only from 99. Early days would be 1993 to 1997. 

> Thanks for offering me to use the database on the host. However, I
> still prefer a containerized MariaDB. With a container I do not have
> to manually intervene when the database crashes. Docker simply spins
> up a new container with an uncorrupted MariaDB image without any loss
> of data.


> A similar story holds for Java. I tried running ShinyProxy directly
>  on the host. The required Java version was not compatible with the
>  Debian installation.

  Not a problem at all since JAVA is not used for anything else.
  
>  Shinyproxy runs in a container but exposes the app directly on the
> host's ports. So, would it be possible to set the A record to that
> port? Or to use a Nginx reverse proxy to link the port the URL is
> pointing to to the port ShinyProxy exposes the app on?

  That is done I think. If you mean a DNS record, it can't be
  tied to a part. 

> Besides that, I am also busy with other matters, including teaching and ongoing research projects.

  I have no one to blame but me but it looks I now
  have about 100000 sick ArchEc files.


-- 

  Cheers,

  Thomas Krichel                  http://openlib.org/home/krichel
                                              skype:thomaskrichel