You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not yet widely used in our field, but it may become increasingly common. Adding it at this stage would require messing up artifacts, which are somewhat complicated to import into the web-app, so we will not be adding it at this stage.
Moreover, at this point RRID is still not widely used in ERP research, so it might be more of an unnecessary extra workload than something really useful for the user to fill it in, but we should keep it in mind in case it starts being more widespread.
The text was updated successfully, but these errors were encountered:
We like this because then the user does not have to input RRID when they pick one of the existing tools, and we can ask about it only if they used "other". But we will leave this for a later enhancement, because it will take time to add all IDs. :)
Agreed for versions, too, we had that in mind, but it is too time consuming at the moment, especially because new versions keep coming out all the time and tracking them for all the software will be demanding. I will open it as a separate issue, so it doesn't get lost here :)
Guiomar has suggested adding RRID - these are unique IDs for tools (software, equipment such as caps or amps). See here:
https://scicrunch.org/resources/ - main page
https://scicrunch.org/resources/data/source/nlx_144509-1/search - search results for Tools, which is a section we may find useful
This is not yet widely used in our field, but it may become increasingly common. Adding it at this stage would require messing up artifacts, which are somewhat complicated to import into the web-app, so we will not be adding it at this stage.
Moreover, at this point RRID is still not widely used in ERP research, so it might be more of an unnecessary extra workload than something really useful for the user to fill it in, but we should keep it in mind in case it starts being more widespread.
The text was updated successfully, but these errors were encountered: