Bookmark Menu

Vivek_Patel

I frequently find myself bookmarking Onshape documents that are public but not copyable - that I want to come back to for reference. If I could have a system inside of Onshape where I could “save” /  “bookmark” these documents inside of Onshape.

Henk_de_Vlaam

Can using "Labels" help you?

S1mon

Depending on what you want to go back to, you could create your own "bookmark" assembly with a part or assembly from the public documents, and then you can "open linked document" to go to the original.

If the names of the parts or assemblies or their shapes are not enough to trigger your memory, you could put them in folders that you name with your own text. You could also add your comments to the inserted parts/assemblies.

Evan_Reese

I think labels are the solution here. They are a per-user thing, so you can add them to any doc you want, even other people's public ones. No one else will see the labels you put on documents (I'm pretty sure). It's just for you to organize your stuff how you like.

nick_papageorge073

I'm missing something.... every onshape document made by a hobby plan is public, and fully copyable.

S1mon

A copy is not necessarily in sync with the latest developments of a public file. If that's important to you, then it sounds like labels are a good solution. I haven't used them yet. The one reason to use an assembly as bookmark file is that as far as I know, labels are not synced throughout a company. 

matthew_stacy

Evan_Reese said:

I think labels are the solution here. They are a per-user thing, so you can add them to any doc you want, even other people's public ones. No one else will see the labels you put on documents (I'm pretty sure). It's just for you to organize your stuff how you like.

Labels might form the embryo of a solution, but last I checked, they only offer a single layer for categorizing documents.  Hierarchical, nested labels would provide vastly more utility.

In my opinion it would also be useful, for non-enterprise users of Onshape, to be able to share that bookmarking structure, both for consistency, and to eliminate duplication of effort.

In the short term, perhaps some clever API developer will offer us per-user and shared-user bookmarking utilities (...perhaps with a robust AI-based search engine, built-in).