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.
Why doesn't the documents creators name follow along with copies - or copies of copies?
Answers
-
As a follow up - this is my suggestion for what changes would look like.In the "version & history" tab of the copy, the first version should have a button that links a URL to the original model, Then list the new owner with the label of "copy" attached to first version (do not change any other aspect - make it work just like it doe's now). This URL link and label of "copy" should propagate into all other copies no matter how other copies are made (copy from copy situation). This label "copy" should be seen in the "public document list" the same way as it does as if you make a copy of your own work.If the original document is deleted, then the link would simply fail (no harm , no fowl)The person that copies, should still have full rights to make edits to that copy, because it is a public document, and they still own that copy from that point on, into the future. They would technically "own" a "copy of a document" not a "stand alone document" that is untraceable to it's "origin".I know this sounds like semantics, but I think this would accomplish several goals1) teachers could track students work for authenticity easier2) people could find originators so they can give out likes. (and we could here from our peers about our work).3) make it more difficult to use other's work (undetected) - OK I admit this one is kind of a stretch, (and I have never seen an example of this),(but ... still)Even if this couldn't be made backward compatible - I still think it would be an improvement worth implementing at this time.Once again I'd like to say, I don't want to change how copies work, just add some features to trace originality.I'm a big fan of Onshape and I know this seems like a small issue - but I think others might benefit from the changes too.Are there other issues at play, or changes that I might have overlooked?0
-
Changes made should just be logged in the versions, including the user who made them. I thought this was standard behaviour?
0 -
martin_kopplow said:Changes made should just be logged in the versions, including the user who made them. I thought this was standard behaviour?I don't think that's how copies behave.I don't have a problem with people copying, or owning that version of the copy. Just wish I got credit for being the originator.I have looked at copies of my work that other people have made & can't find a way to trace it back to me. Maybe I'm missing something - but I don't see how to do it. If there is a way, I'd like to know how.0
-
Agreed, It would be nice to be able to credit the original creator of a model.
3 -
I think copy history is a crucial feature that needs to be added. When searching through public docs to try and find something useful I find hundreds of copies, often with no modifications since the copy. Many of them have edited the default document title to remove the "copy" bit or completely rename them. This makes it really really hard to find the original source. Since copies don't copy the history, these copies also have no indication of what version they are a copy of, and often they are copies of old versions that include bugs etc that the original author has fixed in followup versions.
It is possible to manually add heritage information and version history into versions, notes, featurescript comments, etc, but nobody does because it's a burden, and most people making copies never really intend them for public consumption, they just want to play around with it.
Just adding the url to the version that was copied in the initial copy would be a huge help. Even better would be to pre-pend the url to a list of copy urls take from the copy, so the initial version has the full copy-history all the way back to the original. This saves you from having to follow the links all the way back to the original, you can just jump to it directly.
There are many many other threads asking about how to determine copy history that this would resolve. I realise it might not be possible to add these links retroactively, but at least having them for future docs would be great.
4 -
@dbaarda - I like your idea for URL link to original, following along with all future copies. I don't want to change the way that copies work now, just want to add that traceability function.
0 -
Regarding (by @dbaarda ) . . . When searching through public docs to try and find something useful I find hundreds of copies, often with no modifications since the copy . . . and most people making copies never really intend them for public consumption, they just want to play around with it.
I think a good solution to this would be having the option to make a soft-copy, temporary-copy, call it what you want. A copy which maybe deletes/purges itself after 30 days unless some key word is removed from its title/name.
I find myself manually deleting such copies I've made all the time. But what if I didn't? What if most people didn't? What a waste of space. A public gallery that's all haystack with very few needles.Unemployed Onshaper- Operating on European time - More of me here ➤➤ https://linktr.ee/Liam.G0 -
0



