What functionality is missing? What is unsatisfying with the current situation?

  Have a way to import a language dictionary into a variable collection.   The functionality missing is being able to hover over words from your conlang to see their translation. Currently this is achievable via variables, however the language article also has a dictionary section which is a closely related function.   The unsatisfying part that it is currently impossible to operate a dictionary and a variable collection from the same csv, due to some fields indicating entirely different values and being required in one while optional in the other. This means that you have to double book keep.  

The technical issue and a possible solution

  For variables all four columns are required.       For dictionaries only the first and fourth columns are required       As we can see the first and fourth columns line up, the first column in both is the word being used, which is a fine match for a key. The fourth column contains the value which is the meaning of the world, which is a perfect match.   However the second and third column outright clashes. These two are optional with dictionaries, however if we leave them out then the csv imported resulting variable will be a number (as that is the only one which operates on key-value required only).   One possible solution is to add an "Import Dictionary CSV" or something similar button under the #collection_import_submit button in the variables section. This button will do standard csv import with the following method to adhere to the dictionary exported csv format:  

1. key is imported as the string combination of spelling + translation - why? because spelling is not enforced to be unique by the dictionary function, however it is highly unlikely to have a record appear twice in it with the same spelling and translation
2. title is imported from the first column - aka spelling, this will be the displayed word, the word in the conlang
3. type is replaced with simple term in all cases when using import dictionary csv as there is no equivalent to type in the dictionary export
4. value is imported as regular - aka the translation, what we want to display when hovering over the variable

    Example dictionary export with only the spelling and translation filled out to better visualize how it's structured:        

How does this feature request address the current situation?

  Currently there is no synergy between the csv export and csv import functions. It feels like they were just tagged on there to tick a feature, which is fine (especially cause that's also what we did at my last workplace where the client required csv export for each function), but also something that can be improved upon.   Also the current situation is that worldanvil provides no benefits to keeping conlang records in dictionaries over keeping them in a txt file (you can also search within a txt file). With this the dictionary csv export could be a useful feature.   The variables are great, so currently the best solution is to use a csv file as the main dictionary and then import variables, there is no benefit to using the dictionary section from an author's perspective.

What are other uses for this feature request?

  Being able to have one unified csv per language for your world. Doing simple variable CSV imports without needing to fill out title and type.