Difference between revisions of "SS P03 10AUG2015"

From PHUSE Wiki
Jump to: navigation, search
(Created page with "Attendees Mike Agenda: 1. Agree on directory structure proposal 2. Discuss how to move what we have to that new structure 3. Decide on how to update the index page to point ...")
 
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
Attendees
+
'''Attendees
 +
'''
 +
 
 +
Mike Carniello
 +
 
 +
Mike Schembri
 +
 
 +
Gustav
 +
 
 +
Rebeka
 +
 
 +
Peter
 +
 
 +
Adrienne
 +
 
 +
Hanming
 +
 
 +
Jeno
  
Mike
 
  
 
Agenda:
 
Agenda:
1. Agree on directory structure proposal
+
#Agree on directory structure proposal
2. Discuss how to move what we have to that new structure
+
#Discuss how to move what we have to that new structure
3. Decide on how to update the index page to point to github content, non GoogleCode content
+
#Decide on how to update the index page to point to github content, non GoogleCode content
  
  
Line 12: Line 28:
  
 
Point 1: Scripts
 
Point 1: Scripts
 +
 
First Level: Contributed or Qualified
 
First Level: Contributed or Qualified
 +
 
Second Level: White Paper Main Topic
 
Second Level: White Paper Main Topic
Third Level: White Paper Sub Topic
+
 
 +
Third Level: White Paper Sub Topic (Expect different subtopics for each different Main Topic)
 +
 
 +
 
 +
Some more discussion on this.
 +
 
 +
Some advocate topic first, then contributed/qualified.
 +
 
 +
Some advocate contributed/qualified first, then topic.
 +
 
 +
Some don't care, as they believe the Script Index is the focus.
 +
 
 +
'''Proposal:'''
 +
 
 +
1) Go with Contributed/Qualified as first level in working directory structure
 +
 
 +
2) In the Script Index, flag scripts as being qualified, contributed, or regulatory-contributed scripts.
 +
 
 +
3) If a script is in multiple stages, only publish the latest stage.
 +
 
 +
 
 +
Okay: we have consensus on this!!!
 +
 
  
 
Point 2: Data
 
Point 2: Data
 
First Level: sample, test, ADaM pilot datasets – flat
 
First Level: sample, test, ADaM pilot datasets – flat
 +
 +
 +
 +
/root/qualified/ae/meddra/example1.sas
 +
 +
/root/data/adam/set1/adae.xpt
 +
 +
/root/data/adam/set1/adae.csv
 +
 +
/root/data/adam/set1/data_readme.txt
 +
 +
/root/data/adam/set2/adae.xpt
 +
 +
/root/data/sdtm/set1/ae.expt
 +
 +
/root/data/sdtm/set2/ae.expt
 +
 +
 +
Consensus???
 +
 +
Yes!
 +
  
 
Point 3: Documentation
 
Point 3: Documentation
Bundled with scripts (as is output, logs, etc.)
+
 
 +
Bundled with scripts (as is output, logs, etc.)??
 +
 
 +
 
 +
We've reached consensus on this: /root/qualified/ae/meddra/example1.sas
 +
 
 +
Do we document like this?: /root/qualified/ae/meddra_user_manual.txt
 +
 
 +
Do we document like this?: /root/qualified/ae/meddra/user_manual.txt
 +
 
 +
Do we document like this?: /root/qualified/ae/meddra/documentation/user_manual.txt
 +
 
 +
We will discuss in mail!
 +
 
 +
 
 +
'''HOW DO WE MOVE WHAT WE HAVE TO THIS NEW STRUCTURE?
 +
'''
 +
 
 +
Hanming: These steps:
 +
 
 +
# Make a local version of the github content
 +
# On the local machine, create the new structure and move contents into it
 +
# Upload that updated local content to github
 +
 
 +
Who can try to do this?
 +
 
 +
Chris Butler can try to do this?
 +
 
 +
We will take Chris' silence as agreeing to this. :)
 +
 
 +
 
 +
'''Decide on how to update the index page to point to github content, non GoogleCode content
 +
'''''''''
 +
 
 +
Hanming will try to do this - update the index page to point to github content - but only should do this after it's been moved.
 +
 
 +
 
 +
One question:
 +
 
 +
We had as columns:
 +
 
 +
Name, Title, Source, Type, Language, Keywords, Qualification
 +
 
 +
but they all didn't display in a browser.
 +
 
 +
 
 +
So we choose to display columns:
 +
 
 +
 
 +
Name / Title / Qualification
 +
 
 +
 
 +
(with the recommendation that we be sure to put language into the Name extension: eg demo.sas, demo.R )
 +
 
 +
 
 +
What should the link open to? The script ? The folder ? The documentation ?
 +
 
 +
Let's raise that in mail.
 +
 
 +
 
 +
Mail:
 +
* what we agreed to
 +
* what question we have: data folder
 +
* what question we have: what should the link from the index page open?
 +
* action: Chris to use github to make new structure and migrate (mike help migrate)
 +
* action: after that, Hanming update index page
 +
 
 +
 
 +
 
 +
 
 +
.

Latest revision as of 10:53, 10 August 2015

Attendees

Mike Carniello

Mike Schembri

Gustav

Rebeka

Peter

Adrienne

Hanming

Jeno


Agenda:

  1. Agree on directory structure proposal
  2. Discuss how to move what we have to that new structure
  3. Decide on how to update the index page to point to github content, non GoogleCode content


Three Point Proposal:

Point 1: Scripts

First Level: Contributed or Qualified

Second Level: White Paper Main Topic

Third Level: White Paper Sub Topic (Expect different subtopics for each different Main Topic)


Some more discussion on this.

Some advocate topic first, then contributed/qualified.

Some advocate contributed/qualified first, then topic.

Some don't care, as they believe the Script Index is the focus.

Proposal:

1) Go with Contributed/Qualified as first level in working directory structure

2) In the Script Index, flag scripts as being qualified, contributed, or regulatory-contributed scripts.

3) If a script is in multiple stages, only publish the latest stage.


Okay: we have consensus on this!!!


Point 2: Data First Level: sample, test, ADaM pilot datasets – flat


/root/qualified/ae/meddra/example1.sas

/root/data/adam/set1/adae.xpt

/root/data/adam/set1/adae.csv

/root/data/adam/set1/data_readme.txt

/root/data/adam/set2/adae.xpt

/root/data/sdtm/set1/ae.expt

/root/data/sdtm/set2/ae.expt


Consensus???

Yes!


Point 3: Documentation

Bundled with scripts (as is output, logs, etc.)??


We've reached consensus on this: /root/qualified/ae/meddra/example1.sas

Do we document like this?: /root/qualified/ae/meddra_user_manual.txt

Do we document like this?: /root/qualified/ae/meddra/user_manual.txt

Do we document like this?: /root/qualified/ae/meddra/documentation/user_manual.txt

We will discuss in mail!


HOW DO WE MOVE WHAT WE HAVE TO THIS NEW STRUCTURE?

Hanming: These steps:

  1. Make a local version of the github content
  2. On the local machine, create the new structure and move contents into it
  3. Upload that updated local content to github

Who can try to do this?

Chris Butler can try to do this?

We will take Chris' silence as agreeing to this. :)


Decide on how to update the index page to point to github content, non GoogleCode content ''''

Hanming will try to do this - update the index page to point to github content - but only should do this after it's been moved.


One question:

We had as columns:

Name, Title, Source, Type, Language, Keywords, Qualification

but they all didn't display in a browser.


So we choose to display columns:


Name / Title / Qualification


(with the recommendation that we be sure to put language into the Name extension: eg demo.sas, demo.R )


What should the link open to? The script ? The folder ? The documentation ?

Let's raise that in mail.


Mail:

  • what we agreed to
  • what question we have: data folder
  • what question we have: what should the link from the index page open?
  • action: Chris to use github to make new structure and migrate (mike help migrate)
  • action: after that, Hanming update index page



.