search

stevensdavid / jabref

Fork of Jabref for lab in DD2480 at KTH
https://www.jabref.org
MIT License
1 stars 0 forks source link

Make UI mockups for Bibsonomy functionality #8

Open stevensdavid opened 4 years ago

stevensdavid commented 4 years ago

In the old functionality, there was always a popup nagging that test-credentials for BibSonomy are used. This was annoying and I removed the popup at #2157, but it was not quite finished. Proposal is to restrict the number of interactions with the test key and then guide the user to the preferences to set a BibSonomy key.

Blocked by #7

felixlut commented 4 years ago

The resolution of this issue will be presented in the Wiki

felixlut commented 4 years ago

Comments from JabRef:

@felixlut Thank you for the action taken. The place looks right. Please work on a user documentation (pull request on https://github.com/JabRef/user-documentation), too. Maybe as a walk-through using the feature. - Good work!

Comments:

1. Settings: Yes!

2. Full Text and Tag search: "Adding separate entries to the Web Search" is good. The other one is not integrated in JabRef.

3. Tag cloud. Not sure about the second drop down. Maybe, we need to keep it there, because the setting will be changed frequently. Future will tell ^^. You could add Telemetry to it. Maybe you find other code doing that.

4. Filter found entries: Reuse is great.

5. Export to BibSonomy and Deleting entries: Looks OK for a first implementation. Advanced implementatoin: A user has a bibsonomy account with references in there. He connects JabRef to it (already in scope). JabRef automatically fetches the entries and updates them in Bibsonomy. Similar to https://docs.jabref.org/collaborative-work/sqldatabase, but with BibSonomy as "backend".

6. Export to BibSonomy and Deleting entries: "Set read status". JabRef already has "special fields" (https://docs.jabref.org/fields/specialfields) for read status. Maybe, you can use that storage for that BibSonomy feature (maybe data mapping?).

7. Synchronize and Download documents: My comment on "Export to BibSonomy" also applies here: Similar to https://docs.jabref.org/collaborative-work/sqldatabase, but with BibSonomy as "backend"

8. Synchronize conflict resolution: Please look for the "Merge Entries Dialog". Refs #6021. https://docs.jabref.org/finding-sorting-and-cleaning-entries/mergeentries. You can just call it. Refs #5688.

9. Proxy Settings: Yes

10. Test-Credentials: Yes. I would open the popup only at WRITE actions. Not at the first interations with BibSonomy. Otherwise, it is very disturbing. You know, the just hopping by and playing around thing. This should be easy and not disturbed by a dialog.

BibSonomy should change the user workflow as less as possible. -- Saying that, the Tag Cloud is prio 3. Prio 1 is the thing you described. Prio 2 is that the user can sync his database with BibSonomy.

koppor commented 4 years ago

Thank you for working on this. Is there a chance that you keep on working?

felixlut commented 4 years ago

Hello, and sorry for the late response. I can't make any promises, as the course have now concluded, and new ones have begun. I would like to complete this however, since the "boring" part is done! It will depend on how time consuming the upcoming courses are.

koppor commented 4 years ago

If you want, we can do smae #earlymobbing or #latemobbing once a week or so ^^. -- https://github.com/ungerts/remote-working-link-collection/ 😄