User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
When implementing this consider: how is copying different from creating a new version?
My initial guess is that "creating a new version" essentially replaces the old version (the original module), whereas "create a copy" would create a brand new module that is separate from the original module. This guess should be confirmed before implementing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Creating new new version right now makes a copy of the module you created a new version of. There is not a difference between creating a new version and copying. I am not sure if there are extra expectations between the two but from the way I see it they are the same. If users wanted to start over they could always create a new module. It seems like this is what you are talking about.
Last edit: Christopher Macco 2014-06-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Chris - Let's discuss this one when I'm back next week - GH
From: Christopher Macco [mailto:cmacco@users.sf.net]
Sent: Thursday, June 26, 2014 1:12 PM
To: [edrepo:feature-requests]
Subject: [edrepo:feature-requests] #62 Create copy of module
Creating new new version right now makes a copy of the module you created a new version of. There is not a difference between creating a new version and copying. I am not sure if there are extra expectations between the two but from the way I see it they are the same. If users wanted to start over they could always create a new module. It seems like this is what you are talking about
Status: open
Group:
Labels: Interface Improvements
Created: Mon Nov 19, 2012 07:03 PM UTC by Jon Thompson
Last Updated: Mon Nov 19, 2012 07:03 PM UTC
Owner: nobody
User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
Implemented "Copy" button at revision #316. This gives the user the ability to make a copy of the current module they are editing. This button was not implemented but the shell and some of the code was there. I implemented a working button in the edit module menu. As of now I do not see a difference between copy and making a new version so I just implemented one button for now. This was tested using Firefox, Windows 8.1 Pro, XAMPPLite 1.7.3.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is a difference between copying and creating a new version. The versions of a module are linked to each other, and there is a version number that changes as you move from one version to the next. The idea for copying is to create another module that is not linked by a version number (and that may have a different name). If you've taken the "new version" capability away, we should role that change back and restore it (this is where version control helps!). We can discuss copy next week if you'd like.
GH.
From: Christopher Macco [mailto:cmacco@users.sf.net]
Sent: Thursday, June 26, 2014 1:51 PM
To: [edrepo:feature-requests]
Subject: [edrepo:feature-requests] #62 Create copy of module
Group: --> Next_Release_(example)
Priority: 5 --> 1
Comment:
Implemented "Copy" button at revision #316. This gives the user the ability to make a copy of the current module they are editing. This button was not implemented but the shell and some of the code was there. I implemented a working button in the edit module menu. As of now I do not see a difference between copy and making a new version so I just implemented one button for now. This was tested using Firefox, Windows 8.1 Pro, XAMPPLite 1.7.3.
Status: open
Group: Next_Release_(example)
Labels: Interface Improvements
Created: Mon Nov 19, 2012 07:03 PM UTC by Jon Thompson
Last Updated: Thu Jun 26, 2014 05:12 PM UTC
Owner: nobody
User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
Yes, I would like to discuss the copying modules versus creating a new version next week. I did not take out the ability to create a new version I just added a button to use the code for this, but next week after we talk I will fix what I need to and figure out how to implement this feature.
There is a difference between copying and creating a new version. The versions of a module are linked to each other, and there is a version number that changes as you move from one version to the next. The idea for copying is to create another module that is not linked by a version number (and that may have a different name). If you've taken the "new version" capability away, we should role that change back and restore it (this is where version control helps!). We can discuss copy next week if you'd like.
GH.
From: Christopher Macco [mailto:cmacco@users.sf.net]
Sent: Thursday, June 26, 2014 1:51 PM
To: [edrepo:feature-requests]
Subject: [edrepo:feature-requests] #62 Create copy of module
Implemented "Copy" button at revision #316. This gives the user the ability to make a copy of the current module they are editing. This button was not implemented but the shell and some of the code was there. I implemented a working button in the edit module menu. As of now I do not see a difference between copy and making a new version so I just implemented one button for now. This was tested using Firefox, Windows 8.1 Pro, XAMPPLite 1.7.3.
feature-requests:#62http://sourceforge.net/p/edrepo/feature-requests/62/ Create copy of module
Status: open
Group: Next_Release_(example)
Labels: Interface Improvements
Created: Mon Nov 19, 2012 07:03 PM UTC by Jon Thompson
Last Updated: Thu Jun 26, 2014 05:12 PM UTC
Owner: nobody
User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
Created: Mon Nov 19, 2012 07:03 PM UTC by Jon Thompson
Last Updated: Thu Jun 26, 2014 05:50 PM UTC
Owner: nobody
User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
Implemented at revision #321: This gives the user the ability to create a new version of their module or create a copy of their module. The difference between create a new version and create a copy: Create a new version creates a new module with the same information and BaseID (which means the same non-editable title) of the original module. It will also update the version number corresponding to the current new version. Creating a copy will create a new module with the same information as the original but will be completely separate from the original module (this title can be edited). I tested this using two different users ("Submitter", "Admin") and I tested creating a module, creating a new version, and creating a copy. I looked in the database to compare the data to what it should be. I tested this multiple times with different information before I commit the code. I tested this on: EdRepo v.08, Windows 8.1 Pro, XAMPPLite 1.7.3, Firefox.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When implementing this consider: how is copying different from creating a new version?
My initial guess is that "creating a new version" essentially replaces the old version (the original module), whereas "create a copy" would create a brand new module that is separate from the original module. This guess should be confirmed before implementing.
Creating new new version right now makes a copy of the module you created a new version of. There is not a difference between creating a new version and copying. I am not sure if there are extra expectations between the two but from the way I see it they are the same. If users wanted to start over they could always create a new module. It seems like this is what you are talking about.
Last edit: Christopher Macco 2014-06-26
Chris - Let's discuss this one when I'm back next week - GH
From: Christopher Macco [mailto:cmacco@users.sf.net]
Sent: Thursday, June 26, 2014 1:12 PM
To: [edrepo:feature-requests]
Subject: [edrepo:feature-requests] #62 Create copy of module
Creating new new version right now makes a copy of the module you created a new version of. There is not a difference between creating a new version and copying. I am not sure if there are extra expectations between the two but from the way I see it they are the same. If users wanted to start over they could always create a new module. It seems like this is what you are talking about
[feature-requests:#62]http://sourceforge.net/p/edrepo/feature-requests/62/ Create copy of module
Status: open
Group:
Labels: Interface Improvements
Created: Mon Nov 19, 2012 07:03 PM UTC by Jon Thompson
Last Updated: Mon Nov 19, 2012 07:03 PM UTC
Owner: nobody
User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/edrepo/feature-requests/62/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Feature Requests:
#62Implemented "Copy" button at revision #316. This gives the user the ability to make a copy of the current module they are editing. This button was not implemented but the shell and some of the code was there. I implemented a working button in the edit module menu. As of now I do not see a difference between copy and making a new version so I just implemented one button for now. This was tested using Firefox, Windows 8.1 Pro, XAMPPLite 1.7.3.
Hi Chris,
There is a difference between copying and creating a new version. The versions of a module are linked to each other, and there is a version number that changes as you move from one version to the next. The idea for copying is to create another module that is not linked by a version number (and that may have a different name). If you've taken the "new version" capability away, we should role that change back and restore it (this is where version control helps!). We can discuss copy next week if you'd like.
GH.
From: Christopher Macco [mailto:cmacco@users.sf.net]
Sent: Thursday, June 26, 2014 1:51 PM
To: [edrepo:feature-requests]
Subject: [edrepo:feature-requests] #62 Create copy of module
Implemented "Copy" button at revision #316. This gives the user the ability to make a copy of the current module they are editing. This button was not implemented but the shell and some of the code was there. I implemented a working button in the edit module menu. As of now I do not see a difference between copy and making a new version so I just implemented one button for now. This was tested using Firefox, Windows 8.1 Pro, XAMPPLite 1.7.3.
[feature-requests:#62]http://sourceforge.net/p/edrepo/feature-requests/62/ Create copy of module
Status: open
Group: Next_Release_(example)
Labels: Interface Improvements
Created: Mon Nov 19, 2012 07:03 PM UTC by Jon Thompson
Last Updated: Thu Jun 26, 2014 05:12 PM UTC
Owner: nobody
User should be able to select a module and "create a copy" -- which makes an exact duplicate module (perhaps with a new title provided by the user) that then belongs to the user making the copy and has "In Progress" status.
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/edrepo/feature-requests/62/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Feature Requests:
#62Dr. Hislop,
Yes, I would like to discuss the copying modules versus creating a new version next week. I did not take out the ability to create a new version I just added a button to use the code for this, but next week after we talk I will fix what I need to and figure out how to implement this feature.
--
Thank You,
Chris
On 06/26/14, Gregory Hislop hislop@users.sf.net wrote:
Last edit: Christopher Macco 2014-06-26
Implemented at revision #321: This gives the user the ability to create a new version of their module or create a copy of their module. The difference between create a new version and create a copy: Create a new version creates a new module with the same information and BaseID (which means the same non-editable title) of the original module. It will also update the version number corresponding to the current new version. Creating a copy will create a new module with the same information as the original but will be completely separate from the original module (this title can be edited). I tested this using two different users ("Submitter", "Admin") and I tested creating a module, creating a new version, and creating a copy. I looked in the database to compare the data to what it should be. I tested this multiple times with different information before I commit the code. I tested this on: EdRepo v.08, Windows 8.1 Pro, XAMPPLite 1.7.3, Firefox.