amarcireau / origami Goto Github PK

The attachments will end up taking a lot of space if not removed. The following policy could be applied:

• remove any previous patch with the same major and minor
• keep the previous minor's last patch (as an alternative if the update induced regressions)
• keep the previous major's last minor and patch if the major is strictly larger than one

As an example, when 2.3.2 is released, the following releases would keep their attachments:

• 2.3.2 (current)
• 2.2.5 (previous minor's last patch)
• 1.4.8 (previous major's last minor and patch)

Sometimes, the graph zoom seems to jump. Exact circumstances not found yet.

Hello,
It would be nice to handle short DOIs, like "ckpd".

Seems like some refactoring is needed to do so. What do you think about it?
Chiptuned

Zoom keeps jumping. Source not identified.

Adding a suggested, existing DOI should promote it to "in collection" and trigger requests. So far, it only promotes it.

Check if the behavior is as expected with BibTeX imports.

Some authors have no first name, which is shown as 'undefined' by Information and PublicationsList.

Several messages are printed when opening the application from a terminal, such as: "2017-11-23 15:40:18.658 Origami Helper[1796:13431] Couldn't set selectedTextBackgroundColor from default ()".

Try to find the cause for these messages. Different platform may generate different messages.

And a tab that can be used to search for an article in the collection.

The header seams to pose a problem:

Automatically generated by Mendeley Desktop 1.17.12
Any changes to this file will be lost if it is regenerated by Mendeley.

BibTeX export options can be customized via Preferences -> BibTeX in Mendeley Desktop

@article{Mead1988,
abstract = {An analog model of the first stages of retinal processing has been constructed on a single silicon

It would be appreciated to copy a list of DOI and then generate a node graph on it.

On Recaptcha completion, the graph is shown for a little while.

Hi,
First, I wanted to thank you for this great piece of software, it looks like I'll be using it a lot in the future.
Just a small suggestion, I think it would be easier to visualize and understand the graph if it was directed.
Something like: A cites B becoming A -> B instead of the current A - B.

Cheers,

Make DOIs copyable from the Information pane.

Hi,
Is it possible to add a DOI with its http link attached (with the "https://doi.org/" prefix)?
Also, it would be more convenient for me to visualise nodes with the first letters of the author and the year (the 2 last digits), for instance "Go99" for a 1999 paper from Tim Gollish, and so on.
Thanks

Hi again,
I've seen in an older issue that you were planning on gathering cited papers and not only cited-by papers (#3). Is this still in plan?

From what I understood the main concern at the time was the lack of source to get this information. But it seems that in the mean time crossref has added this field (for some of their papers), otherwise scopus API also has it (https://academia.stackexchange.com/questions/106790/api-to-get-citations-from-doi).

Cheers,

Seb

Should also not mess with click-and-drag behavior.

It would be great to have the release name at least somewhere in the app.

This feature requires to add a knownDois set object to the state.

Some articles (as an example, 10.1007/s00221-003-1446-0 or 10.1007/BF00238522) do not have the expected release date.

Sort BibTeX entries before saving them.

Idea for a new display: have a chronological order of the papers' network.
e.g. http://bl.ocks.org/robschmuecker/7880033
or https://bl.ocks.org/mbostock/4063570

Write a tool to debug and/or correct a JSON state file (js utility for devs and beta-testers).

Add a stronger filtering to authors (see 10.1101/196139) to avoid 'undefined'.

Add an app version number to saved files, in order to manage retro-compatibility in the future.

Add a user guide describing the software feature and capacities, with screenshots, and a documentation describing code organisation.

These improvements probably involve a README.md refactoring.

Re-importing exported BibTex sometimes fails.

Show cited articles in yellow in PublicationsList as well.

One nice feature would be to import nodes from a BibteX (in the current version, that would imply that only the DOIs of papers would be imported), then if we export as BibteX, it would be "consolidated".

Hello,

I propose to be able to change the node color and stickyness and other node options via a right-click on nodes in the graph, or element in list, or element in regex search (if the paper is imported).

Thanks!

Hi,
The relation between two nodes are sometimes ambiguous and I need to click on one of the two nodes in order to see the papers which are citing the papers, aka the green nodes.
Could we have another color for "citation" papers?
Is it relevant in the current state of development?

In this case, with a dense graph, I don't know the relation (or let's say folding), between Ca17 and the other nodes, because no one cites it, and I would like to know which ones in my graph are used in this paper.

Consider adding a refractory period for the graph reloading on state change (this could greatly increase fluidity when adding a lot of new publications).

Massive parallelization induces a big performance drop.

Whatever the mode and owning of chrome-sandbow :

[30906:0919/162257.529632:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/dardelet/Origami/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

Hello,
It seems that this feature is not working for me.
You can try it with my save.

ryad_google_dec7.zip

Thanks