Version Naming Conventions

NeilCooke · August 2018

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:

Image: https://us.v-cdn.net/5022071/uploads/editor/al/qwxt4em44c5c.png

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?

Image: https://us.v-cdn.net/5022071/uploads/editor/56/mcll6zx1iudm.png

Thanks.

konstantin_shiriazdanov · August 2018

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.

john_mcclary · August 2018

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

owen_sparks · August 2018

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.

3dcad · August 2018

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?

owen_sparks · August 2018

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.

lemon1324 · August 2018

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.

3dcad · August 2018

It seems like we think alike @owen_sparks

owen_sparks · August 2018

3dcad said:

It seems like we think alike @owen_sparks

I'll chose to take that as a compliment, so thank-you

Owen S.

Version Naming Conventions

Comments

Howdy, Stranger!

Quick Links

Categories