Conversation
Initial commit so that @mheppler can come on board this branch. This is a totally unfinished rough draft of half of the Geoconnect user guide.
Finished user guide page for GeoConnect, including screenshots to help guide users through the mapping process.
Misc typo, grammar, formatting fixes.
Tiny typo fix
Phrasing and syntax improvements based on Raman's review of the geoconnect user guide.
- Explain that we don't recommend sysadmins to install Geoconnect at this time. - For User Guide page, add table of contents (exposed improper nesting, also fixed) and explain that Geoconnect is optional. - Various other tweaks, fixes, and improvements.
There was a problem hiding this comment.
Great work. Much improved from what's in production now. In the User Guide it would be nice to see something about how users can view maps even before we talk about creating them. Maybe some tips on finding maps to look at as well. Please see my other comments in the review itself such as making a dedicated Geoconnect page in the dev guide (like we do with UNF) and other specific comments. I did make a few improvements in aea9ccf
Update: this got buried under "Hide outdated":
Dev Guide: All of this detail here and below about Geoconnect is great but I'm thinking we should have a separate page for it. This page is getting long and the focus should be about setting up a development environment, not a relatively deep dive into a specific feature. I would suggest following the pattern established by UNF, which is even split into multiple pages:
I don't think we want all that detail about UNF on this "Development Environment" page.
| Update "mapitlink" | ||
| ------------------ | ||
|
|
||
| SQL commands to point a Dataverse installation at different Geoconnect servers: |
There was a problem hiding this comment.
In the Geoconnect README we say, "You should wait until the WorldMap rewrite is complete before considering installing Geoconnect." Should we explain on this page that people installing Dataverse are welcome to use the two servers below that are hosted by Harvard?
| - If you want to set some dataset-specific facets, go to the root dataverse (or any dataverse; the selections can be inherited) and click "General Information" and make choices under "Select Facets". There is a ticket to automate this: https://github.com/IQSS/dataverse/issues/619 | ||
| Geoconnect works as a middle layer, allowing geospatial data files in Dataverse to be visualized with Harvard WorldMap. To set up a Geoconnect development environment, you can follow the steps outlined in the `local_setup.md <https://github.com/IQSS/geoconnect/blob/master/local_setup.md>`_ guide. You will need Python and a few other prerequisites. | ||
|
|
||
| How Dataverse Ingests Shapefiles |
There was a problem hiding this comment.
All of this detail here and below about Geoconnect is great but I'm thinking we should have a separate page for it. This page is getting long and the focus should be about setting up a development environment, not a relatively deep dive into a specific feature. I would suggest following the pattern established by UNF, which is even split into multiple pages:
I don't think we want all that detail about UNF on this "Development Environment" page.
| @@ -3,29 +3,146 @@ | |||
| WorldMap: Geospatial Data Exploration | |||
There was a problem hiding this comment.
What percentage of users are going to be viewing maps versus creating them? My guess is that more people will be viewing maps since you don't even need to create a Dataverse account to view a map. You just click the button on the dataset or file page. Given this, before we even talk about creating maps, can we have a short section on viewing maps?
Added a short paragraph explaining how to view a map, per @pdurbin's suggestion
…g in User Guide. [ref #3643]
…info into new Geospatial Data pg. [ref #3643]
5 participants
New Contributors
Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Thanks!
Related Issues
Pull Request Checklist