Move import options from settings to individual page [Probeaufgabe]

[Stephan Doerfel]

Currently each user has an import tab in their settings. This is awkward since a) when you look for an option to import stuff, settings is not the first place to look b) it does not belong to the settings

Remove the current import tab and create an import page. The link to the import page could be a third item in the add post menu.

[Former user]

already a separate tab now

[Daniel Zoller]

The import settings were in a separate tab on settings, but we want to move them from the settings

[Robert Jäschke]

I think instead of a separate entry in the "post" menu we should add this as a separate tab to the "post bookmark" pages (for the Firefox and Delicious import (though I wonder whether this is still used/relevant)).

The JabRef-Layout should be kept under "settings", I think they would fit to the "settings" tab, since they modify the layout of the "custom" export.

Since we also discussed removing JabRef support in the long-term and thinking about how important Firefox/Delicious import is, we could as well just remove the functionality.

[Daniel Zoller]

Because bookmarks and publications are only imported once (or once a month), I don't like the idea to add tabs to the post* dialogs. I would suggest to keep the add bookmark/publication pages as simple as possible. But I also don't like that the import is the third entry in the add post menu. Any ideas?

The JabRef Layout is still under settings.

[Robert Jäschke]

Well ... have a look at /postPublication - many of the options there are not used. I think for /postBookmark it's even simpler: who's actually using that page?

[Daniel Zoller]

Yes we have to work on postPublication, too. The post* should be simple and not complex. It's one of our most used features. We should work on postPublication and keep postBookmark as simple as possible.

From 1st till 10th we had ~42,000 request on /postPublication.

[Robert Jäschke]

OK. Then I don't know where to put such an "import" page. From what it is doing (adding posts), it fits to "addPost". We also aim at implementing other import/export options (e.g., ORCID) which should go to the new page then as well. From how this works (once or regularly) it would also fit to the page for the synchronization settings. (Conceptually, an import/export is a one-time-synchronization with a dedicated system.)

[Stephan Doerfel]

Hi, based on gut feeling I side with Daniel on this. My preferred version would be four entries of the addPost Menu:

• post Bookmark
• post Publication
• import Bookmarks
• import Publications

(Mabe instead of the latter two one entry "import" would suffice.)

The import page(s) would be a new dialogue similar to the one we have n the settings. postBookmark and postPublication would link to the import page so users are aware of the option. (Something like: Here you can add a new publication. Use <a>import</a> to mass-import more than one publication.)

I would also endorse a simplified postPublication dialogue. E.g. moving the file-import tab to the new import page. BibTeX/Endnote Import is a candidate for both. Maybe keep a simpliefied version (intended for use with a single publication entry) and move the big complex one with override options etc. to import. Regarding sync: I would keep it in the settings, but definitely link it from the import page.

I think this might actually simplify the relatively complex postPublicationController, simplify the workflow and improve the visibility of our import options. Particularly when we add new ones, like ORCID.

However I am aware that this is a larger reconfiguration and moving of code. So this is not me saying lets do it. Rather my two cents on the conversation.

[Robert Jäschke]

I am against having more options in the post menu. Actually, I prefer a more radical solution (cf issue #2103) which is quite the opposite: having an "addPost" page only, which only has a text input field where the user can enter

• a DOI
• an ISBN
• a URL
• a BibTeX or RIS snippet
• whatever

and then BibSonomy automatically processes the input and chooses the right post type. We could add (initially hidden) options for setting post visibility, etc. although this can anyway be done on the specific post dialogue in the next step. All other "import" functionality (Delicious, Firefox/BibTeX/EndNote files, ORCID, etc.) should then be put on a separate "import" page (I have no good idea, though, where to link it ;-).

[Daniel Zoller]

thx!