Corwin Kerr

> What are the differences in semantics between "project workspace" and "project data space"? Or are they synonyms? @joaander I've found 2 definitions of "data space" in the docs: -...

> the solution that you proposed (allowing jobs to themselves contain workspaces) is precisely what @csadorf and I were trying to get at when we discussed the long-term roadmap @vyasr...

Thank you for clarifying that!! I'll add a note about it to my comment but preserve my expressed confusion.

>It is confusing for users (especially new users) when more than one word describes the same thing. Totally agree! Issue tracking glossary: https://github.com/glotzerlab/signac-docs/issues/59 Google doc on defining terms: https://docs.google.com/document/d/1_merhcK3ohas4IloE616yL7gypMRFcaQLh2oChExC7o/edit?usp=sharing

Now that #685 and #752 and I think all that is left of this issue is to phase out the use of "data space".

@stale-bot this is not ready to be closed. This should remain open because "job workspace" still returns many hits in the next branch. ``` ./signac/__main__.py:912: help="Print the job's workspace path...

I can see another use case: saving a plot from an aggregate back to the project directory for display using the dashboard project overview.

I agree that removing `groupbydoc` will fix this as long as `groupby` is documented.

> I think we should raise an error here generally, and also remove `incomplete_links` in favor of `links` I added the error in `import_export.py` but as I was trying to...

How shall I test this?