@matthiasgeiger thank you for your feedback, I think there are some important points to adress here.

The Web part: It is right that not all of the fields in this tab are web-based. But as you stated, the URL is definitely web based and as the DOI has digital in its name, it would also fit here. Crossref was always described to me as an ID of the project found at crossref.org, but I might be misinformed on that matter.
Apart from these cases, ISBN and ISSN are surely not web based, but the reason to call the tab Web Resources anyway was the following: While some of the listed fields are not originally dependent on the web, the user is given the possibility to interact with them like that. The automatic search for an ISBN or the update of an entry through it is done by connecting with the web. So while the information in the field is independent from the web, the interaction with it is not.
Include Identifiers in name: As you said, it would be possible to just make an Identifier tab by excluding the URL (and possibly crossref?) and this was actually my first approach to the problem. But in a card sorting task, most of the time participants grouped the URL with the identifiers (see figure with co-occurences at bottom), making the current solution more fitting.
While the URL could also be grouped with the file field, this would have interferred with the design of the Attachments tab (see Entry Editor: new Attachments tab #4691 ). But a redesign in that matter would be possible, of course and maybe more clear to the users.
The button layout/design: I am not enirely sure if your problem is only with the layout of the buttons or their design as well. The design of the buttons is of course something than can be changed to better fit the theme of JabRef and should just be consistent throughout the application. I would just not advise to make the buttons completely flat (i.e. no color, no shadow) or to make them too small.
The layout for the buttons was mainly a way to show a clear pattern of possible interactions with the available fields. For this it is not necessary that the buttons are outside of the text fields, but I am not sure if placing them inside the text field is helping the user or looking more appealing.
Text on buttons/tooltip: I am convinced that using icon-only buttons should be limited to cases where an icon has a clear and completely unambiguous meaning in a certain context and that text should be the default if possible. This does, however, not concern the tooltips at all. I never meant to remove or even change the tooltips and I believe that they are a great additional guidance for the user. So that should not be a problem.

@tobiasdiez I also think that discussing that matter in the devcall would be a good idea, I will try to be there. And I can of course update the issues for the entry editor, if changes are "approved".

Description of Issue	Possible Solution	Warnings
Identifiers are split between tabs, although they are similar; URL is associated with the identifiers by the user	create Web resources unifying identifiers from General ,Optional Fields and URL in one tab;	-
button layout is unclear	unified button layout for all fields	More buttons can be added if a function becomes available
-	-	other changes are found in #4686

Uh oh!

Entry Editor: new Web Resources tab #4689

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions