Difference between revisions of "User Guide for Standard Script Repository"
(→How to resolve conflict of concurrent editing)
|Line 91:||Line 91:|
==How to resolve conflict of concurrent editing==
==How to resolve conflict of concurrent editing==
Revision as of 07:47, 6 February 2013
This repository is for storing standard scripts identified, developed and shared by volunteers who are interested in data transformations and analyses across and/or within a therapeutic area and exploratory analysis. The goal will be to begin the process of standardizing analyses across the industry, but also include examples of what can be done with a standardized data set. This will be a collaborative environment by using Google Code and online wiki to create and add scripts and documents that can be shared openly between industry entities and regulatory agencies.
How to get involved
- Repository Maintainer
- Hanming Tu (email@example.com), one more (?)
- Current members
- Steps to join
- Join the PhUSE mailing list to receive updates http://goo.gl/R8q8V
- Sign up for the PhUSE working group mailings
- Go to www.listbox.com
- Join this group: “CSS WG5: Developing Standard Scripts”
- Sign up to be a contributor or committer in the script repository
- Send an email to one of the repository maintainers to request to join the Google Code PhUSE/FDA script repository
- Go to repository at https://code.google.com/p/phuse-scripts/ and start interacting
What role you want to play?
In Google code, there are two roles that a person can play:
- In then FDA/PhUSE repository, someone able to take on responsibilities for editing, adding and maintaining scripts in the repository. Committers should be prepared to contribute his or her time to share or develop a script and/or commit to work on others’ scripts. Committers should feel that they have the necessary skills and experience to enhance the set of existing scripts in the repository. Committers may recruit additional help from other committers and contributors to develop the script and document milestones of the script advancements.
- This role is designed more for script users, who may occassionally want to participate in editing and enhancing scripts. Do not have write access to the complete library of scripts, but can be given access to individual scripts to work on specific issues. A contributor shall take specific duties in the repository and may participate in the development of specific scripts.
Usually, only Committers may add new scripts. If you are a contributor, you can request to have edit privileges by emailing to one of the repository maintainers.
How to add a new script
You have two methods to add a script:
- using browser or
- using subversion client tool such as TortoiseSVN.
In the repository, go to the sources tab and navigate to the appropriate directory. The directories are organised by scripting language (e.g. R/SAS) and then into analytical or functional areas. Inside each functional area (e.g. the DM directory for demographic scripts), there are 6 directories:
- baks: backup and old versions
- data: example or test data files
- docs: documentation
- result: any outputs files
- src: source code
- valid: validation files
For more information about the folder structure, please review this file: http://code.google.com/p/phuse-scripts/source/browse/trunk/folder_structure_proposed.txt.
Users are encouraged to add documentation when adding a script. There are template documents for User Guides and Specifications documents here (link to be added), and it is strongly encouraged to utilize these documents for new scripts and to follow the recommended name conventions.
Committers will add scripts or packages of scripts as “Downloads” as appropriate. “Downloads” are easily accessible packages of code that can be downloaded by anyone.
Add script through browser
Here are the steps for adding a script through a browser:
- go to the FDA/Script repository: http://code.google.com/p/phuse-scripts/
- Click Source-> Browse->trunk and expand to the folder that you’d like to add a script
- Click “Create” or “Upload” to upload a ready prepared script.
- If you choose “Create”, a simple window with line numbered text editor is opened
- Provide and append a file name in the path field
- Provide description in the commit log field
- Click the “Commit” button.
Caution: if you have not done step 7, your change will not be saved!
Add script through TortoiseSVN
Here are the steps:
- Install TortoiseSVN by following the links listed in http://code.google.com/p/phuse-scripts/wiki/ReadMeFirst or the steps in this file http://www.prosvn.org/download/TortoiseSVN%20-%20Installation%20EN.pdf
- Once you have installed the subversion client, you can check out the whole repository by following the instruction at http://code.google.com/p/phuse-scripts/source/checkout
- Once you have the repository at your local drive, you can navigate to the folder in the local repository and just copy your script to the folder
- Then right-click on the folder, then click the “SVN Commit”
How to edit a script
Only committers or contributors with edit privileges can edit scripts.
The FDA/PhUSE script repository uses a Subversion repository to manage version control. Further information can be found here: http://subversion.apache.org. It is recommended that you use a package to manage Subversion with your operating system. A list can be found by clicking here. For Windows users, there is some experience in the group with the Tortoise SVN package that can be downloaded here (be careful not to click on the download buttons that appear in adverts on the page).
Scripts can be edited directly from the Google code webpage, or via a Subversion package installed on your local computer. Committers can raise an issue with a script to highlight the need for an edit by following the instructions below.
How to flag an issue with a script
Go to the “Issues” tab of the Google Code repository and click the new issue button, completing the details on the displayed form.
How to resolve conflict of concurrent editing
Google Code does not manage concurrent editing of scripts by different users. Processes to handle development by scripts by multiple users are in development.
Last revised by Kevin Kane,02/6/2013