You could enter the data manually or with a button download the data from the network.
What data exactly, and with what 'button'?
I wonder if you're making fun of me.
I hope it's the translator's fault!!!!
What data? Tags?
Name of the artist, Alias, Date of birth, date of death, age (which the program could easily calculate), nationality, a link to the site, if it is a group, a single singer and finally a field to insert the complete biography. Possibly a simple table to insert the discography.
The button? Do you want me to write you the source in machine language?
Same as you, I am only sharing my opinion.
I still don't see (m)any users putting in the effort to manually populate all sorts of artist related tags for the artists in their libraries.
And for that reason I don't think it is worth the time and effort of the developer to try and implement something like this.
What tags are there in the program that refer to the artist?
There is currently only one container, not even a tag, that contains the entire text of the bio.
If they are present they will be hidden!!!!
It is clear that no one tries to populate tags that do not exist.
Also I find the wish a bit vague and general.
Maybe if you would be able to propose something that is more clear and specific, and what would be easier to use I could change my mind.
Do you want it to be precise?
Does this image taken from helium clarify your ideas?
This uses the manual system and the automatic system. See the download button?
If helium wasn't slow and complicated tag management it wouldn't be bad for the idea itself.
I can't be clearer than that. Unfortunately, by using a translator you cannot be sure that everything will be understood.
"Also I find the wish a bit vague and general"
For example, this sentence, translated, has no meaning for me.