I would like to able to access to multiple URL/file links in the symbol fields under eeschema.
Please check the the attachment image of a eeschema pop-up menu in a symbol where "Open Documentation" items are.
In 4.0.7 version:
The Open Documentation item actually open the file/link that defined in .dcm relative the the symbol.
In 5.x version:
This Open Documentation item open what file/link that specified in the datasheet field of the symbol.
What I like to suggest is a difference way. That is:
Around the Opebn Documentation section of the pop-up should have multiple item for multiple available file/link from the symbol. For example we may have a symbol under schematic that having:
datasheet: LINK_A
erra: LINK_B
LINK_C in the .dcm file.
Then the area of Open Documentation should replace with items like:
Open Documentation (This point to LINK_C)
Open Datasheet (This point to LINK_A)
Open Erra (This point to LINK_B)
With this scheme, one use case like mine will be helpful. I like to use .dcm to point to a local file of the datasheet in-case my URL link in datasheet no long valid on the internet. So now I can open my datasheet with/without internet. And if the link are gone. I can use my local datasheet file as a reference to make sure I can search/relocate the new URL link to that correct datasheet of that exact version or whatever.
Also, I can quickly look at the Erra, or any other relative document to this symbol under schematic.
The datasheet field in the lib file is a legacy field. The current behavior is that it is overwritten (if empty) by the one in the dcm file. (The dcm file allows different datasheets for different aliases.)
I doubt this would be implemented even remotely similar in the new file format.
It might be a good idea to include an option for adding any number of datasheets to the new file format. (Some might use this feature to provide alternative links to the same file. Others might want to include additional information. Some manufacturers have multiple datasheets for the same component. Microcontrollers for example often have a user manual and a specification file.)