-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revise Explore Tools documentation to reflect modularity #4429
Comments
dlmurphy
changed the title
Documentation: Revise Explore Tools documentation
Revise Explore Tools documentation
Jan 22, 2018
dlmurphy
changed the title
Revise Explore Tools documentation
Revise Explore Tools documentation to reflect modularity
Jan 22, 2018
This was referenced Jan 23, 2018
Closed
Note that Geoconnect and Worldmap are not considered modular in the same way as TwoRavens. At this point, they are still a core feature of Dataverse that we maintain. Docs should reflect this. |
I just reviewed the entire API Guide as part of pull request #6107 and there's nothing to fix there for this issue so I removed the GitHub Issue label for that guide. |
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
With #3657 we've moved toward treating external explore tools as modular. This new way of looking at external tools in Dataverse requires we rethink the way we talk about them in our documentation. Let's review all mentions of TwoRavens, GeoConnect/Worldmap, and other explore tools throughout all guides to make sure that it's clear that these tools are considered modular, and that any number of other modular explore tools may be present in any given Dataverse installation.
The text was updated successfully, but these errors were encountered: