Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Version Naming Conventions
Hi fellow FeatureScripters!
As you know, it can be a difficult task to find the original document that a custom feature was created in so you can add it to your toolbar. With so many copies of each document flying around, it can look something like this:

However, if you name your versions they stand out a little better - in the image above I have prefixed each version with "Official" or "Original". Any ideas for a better naming convention?
Also, it is worth renaming "Main" to "Official" for when searching for a document from the documents page. Open to suggestions if anybody has a better idea?

Thanks.
As you know, it can be a difficult task to find the original document that a custom feature was created in so you can add it to your toolbar. With so many copies of each document flying around, it can look something like this:

However, if you name your versions they stand out a little better - in the image above I have prefixed each version with "Official" or "Original". Any ideas for a better naming convention?
Also, it is worth renaming "Main" to "Official" for when searching for a document from the documents page. Open to suggestions if anybody has a better idea?

Thanks.
Senior Director, Technical Services, EMEA
3
Comments
-
Version naming can solve the problem to the some point, but you still can't be sure that it is original. Authors name field would give the best guarantee.
3 -
Good idea @NeilCooke , As long as the message gets out to all the FS writers, and people who branch specify that as well.. It should help clear up who's is the original
0 -
I don't think naming conventions is a robust answer here. I think that when a document is copied the copy should have an "I'm a copy" meta data flag set, and we should filter the search on that flag.
Cheers, Owen.Business Systems and Configuration Controller
HWM-Water Ltd6 -
I think this is wider problem in all public docs and makes them almost unusable. Public docs could be awesome library if had better indexing / naming.
What about automatically marking all copies and give option to search/view only originals?
//rami7 -
Also being able to add one's own branch in a public doc would cut down on the copies in the first place...O.S.Business Systems and Configuration Controller
HWM-Water Ltd3 -
I can certainly go through and update version names on my scripts, but I think this is a more systematic issue.
Sorting search by links/copies would help, but really a more Github-like "fork/modify/pull request" workflow (where you can also follow links from forked copy to parent to find the original) would solve this both for FeatureScripts and geometry public documents.Arul Suresh
PhD, Mechanical Engineering, Stanford University3 -
-
Business Systems and Configuration Controller
HWM-Water Ltd0






