When we use maps, it could be useful to put a geolocation from an address, not only the latitude/longitude. Or find an easy way to convert from the address to latitude/longitude.
Best,
Things to do in version: 6.3
- Edited
Eulàlia Mesalles When we use maps, it could be useful to put a geolocation from an address, not only the latitude/longitude. Or find an easy way to convert from the address to latitude/longitude.
As I conceive this: It is not that Dédalo have to implement a whole database with this kind of info (this is HUGE) but maybe there is an internacional service that can be "asked" to return this info in our maps when needed.
Hi
Eulàlia Mesalles it could be useful to put a geolocation from an address,
Yes!, great idea... but as you say:
Eulàlia Mesalles maybe there is an internacional service that can be "asked" to return this info in our maps when needed.
The main problem here is locate an institutional entity to provide the service, some regions or states has a API to get this kind of information, and it could be possible to get this kind of data for them, but if we need to create a specific connection for every region, it will be huge work... so, the idea is right and it could be useful, but we need a data provided before implement it.
Note: google and others private provides requieres a account and paid for X calls to his API, so, for us, this kind of services are not valid.
Someone knows who can provide this kind of data?
Best
I've found Pelias, Seems what we need.
They state
Pelias is a search engine for places worldwide, powered by open data. It turns addresses and place names into geographic coordinates, and turns geographic coordinates into places and addresses. With Pelias, you’re able to turn your users’ place searches into actionable geodata and transform your geodata into real places.
We think open data, open source, and open strategy win over proprietary solutions at any part of the stack and we want to ensure the services we offer are in line with that vision. We believe that an open geocoder improves over the long-term only if the community can incorporate truly representative local knowledge.
Do you want me to ask Manuel Davila if he can improve this service in our Special Tools?
Eulàlia Mesalles Seems what we need.
Hi, thanks to provide this info.
I read the project and and seems an option.
The project has two ways to provide this kind of data
Creating the infrastructure to serve all data by your own. Going in this wat requiere a big server and his maintenance, that implies a mensual cost.
Accessing to the data by his API, they offer a get API key to use his servers, but, it has a mensual cost:
https://geocode.earth/#pricing
elena Do you want me to ask Manuel Davila if he can improve this service in our Special Tools?
It might be a good idea, but rather than implementing in your tool (which might be fine ... ) but if Manuel Davila knows a free data provider by API or if he can help to integrate the solution.
Note: keep in mind that the address field is not on the map, it is in a separate text field outside the map, so the solution should be something that looks at the address text field and modifies the map in the same way that toponym searches move the map with the position of the toponym searched. So, I think that the solution could be more along the observer/observable line than a tool.
Best
20 days later
- Edited
Is it possible to configure the filter for showing only the fields with read or read/write permissions? Sometimes the list is too long and many fields are not useful. Of course it's not necessary but it can facilitate searches.
Same solution for the list of fields when exporting?
- Edited
Eulàlia Mesalles As the project grows it becomes more important so have the availability to filter and search within TIME MACHINE to locate records that have been deleted and eventually you want to review or recover.
Is it possible to implement this feature: the ability to search within Time Machine ?
Yes, is possible to develop this functionality, but is a complex situation that has a lots of implications, we can added in the road map, but I think the development of this feature will need more time than 6.3... because is a breaking feature that requiere a different search engine, it will be different as standard Dédalo filter, because Time Machine is not following the common structure and the search will be totally different.
So yes, but have a little patience... 
Best
10 days later
Alex I'm not sure about it but probably the search engine for Time Machine could be more simple or limited to a certain fields. ID? Name? Title?. As I can see it now it is more a tool to locate easily a deleted file than a "filter" as we use it in other parts of Dédalo.
2 months later
In the "related types" field, to speed up the process of relating types, would it be possible to change the function to a multiselect, so that it is one-time?
Like, for example, this:
This allows you to select the types you want without having to search for them again.
Best!
16 days later
Component History:
The Inspector section still houses the "component history" in version 6. Moving it to the component itself could be an interesting option. Additionally, it would be helpful if the component was in some way "highlighted" to indicate that it is a commentary on changes that should be examined.
13 days later
- Edited
Relations (inspector)
Usability: It could be interesting to have the availability to open a list, at once, with all the registers linked to another register (it could be useful when we are curating data). As an example: I'm on a entity with these relations and I want to open all of them as a list:
It could be interesting to get this with only a click:
The registers linked have to be of the of the same "kind" or project, obviously.
(I hope this explanation makes sense)
7 days later
When deleting records not from the list but from a resource, it appears like that :
We don't have the availability to chose to delete or not diffusion records.
It would be better to unify this, and have this availability in both cases.
Thank you!
6 days later
In another thread, Ali and Alex started a discussion about the fields dd199 and dd200, the automatic register of authorship and date for every new record. Now, those fields are not displayed, and permissions can't be assigned into the respective sections (in fact, every section). It seems that they contain sensitive information for admins but, to me, that is relevant and useful information for every user. In fact that information is always displayed to the right into the inspector when browsing the edit mode. I suggest to keep both fields operative in the filter by default as they were in v5.
Calculations fields, export the data, not the value.
When exporting fields where there are calculations it exports the formula, as follows:
We need to export the actual data not the formula.
Thank you!
To think about it: When deleting a field in one language and there is information in other languages, is it possible to set up a warning or pop up window with all languages, to force the user to review and arrange several languages at a time? Specialy in text fields with a lot of text.
Now the old information remains (shadowed with light grey).
The main issue here is that the calculations could has multiple export formats. In your screen capture the calculation has only 1 value. But other calculations has multiple values as Estat de la consulta dmm1076, it has 14 exportable values:
"closed_afirmative"
"closed_afirmative_percent"
"closed_negative"
"closed_negative_percent"
"closed_count"
"closed_count_percent"
"closed_total"
"answer_afirmative"
"answer_afirmative_percent"
"answer_negative"
"answer_negative_percent"
"answer_count"
"answer_count_percent"
"answer_total"therefore, I'm thinking that calculations will need to be exported in breakdown format always, to get a column by export value, it will open the possibility to use the results as computable values, or the most closed computable value possible because some calculations get text information as Total privació de llibertat mdcat812 that use the approximation of the time of the prisoner in jail and the calculation output is a date with text comments, another case could be the mixed values of Averages numisdata595 that all values could be computables.
Ok, I think that it could be super useful, but we will have some limitations as the translations of the column names, because the widgets are not using the translation system. Maybe we can implement a solution and re-think the output of the calculations in future revisions.
Best
14 days later
Usability issues.
In the inspector area, in relations section:
It's helpful that when you click on a register, a new window appears. But, if you click on another link, it opens in the same window and ovelaps the record.
It is helpful having multiple windows opened at once when curating data to compare information. Therefore, having the availability to choose whether or not to launch a new window could be interesting.
When you right-click on a link in the results list, it opens in a new window. In order to open it in a new tab you must click ATL. Perhaps doing the same could be the solution.
Thank you.
7 days later
- Edited
More usability issues.
In the Control of documentation research, rang of dates is used to indicate sendind and receiving dates
When only one of these dates is indicated, it may be confusing to the user. It could be useful to clarify whether we are talking about a sending date or a reveiving one.