[wiki] Study Variables #9799
[wiki] Study Variables #9799
Conversation
|
|
||
| ### Overview | ||
| This page covers how to set up LORIS with basic parameters for research data. | ||
| In LORIS, and indeed in all of its instances (CBIG, CCNA, xxx, yyy, etc), the names of participants is anonymized by assigning numeric and alphanumeric ID's to them. In this way, the data of a participant is protected from connection to their name or personal identifying information ("PII"). |
There was a problem hiding this comment.
Preferable to not have specific project names in core LORIS (CCNA, CBIG ,...).
I would also rephrase this a bit in the style "LORIS is nto intended to store PII, Identifiers are used for data linkage"
| - Cardinality: Multiple per participant | ||
| - Data dissemination |
There was a problem hiding this comment.
cardinality here is 1 per participant as well just like PSCID and DCCID
| - Cardinality: One per participant per project | ||
| - Main participant identifier | ||
|
|
||
| - [ExteralID] |
There was a problem hiding this comment.
also why is there no section for externalID configuration
| - [Projects] | ||
| - [Sites] | ||
| - [Cohorts] | ||
| - [Timepoints] | ||
| - [Configurations] |
There was a problem hiding this comment.
not sure given the restructure why those are in the Identifiers section here
| The **PSCID** is dependent on the list of sites in the `psc` table of the database, more specifically the `Alias` column that is used for the `siteAbbrev` type in the generation of the ID. Please refer to the [Sites Parameter Setup](03_Sites.md) page for more details. | ||
|
|
||
| The **PSCID** is also dependent on the list of projects in the `Project` table of the database, more specifically the `Alias` column that is used for the `projectAbbrev` type in the generation of the ID. Please refer to the [Projects Parameter Setup](02_Projects.md) page for more details. | ||
| I feel that this file is not needed No newline at end of file |
There was a problem hiding this comment.
remove this and delete the file isntead
| [](#) | ||
|
|
||
|
|
||
| CandID is an unique numerical ID given to each participant on a per study basis. This ID is typically 6 digits long, however, recently, more digits have been added.Used internally, its principal purpose is for data relationships within the database. It is found in the following database tables: |
There was a problem hiding this comment.
its not per study, its per instance. it is also no longer 6 digits, you dont need to mention that at all the history is not relevant here. Its primary purpose is debatable. its no longer used for data linkage cause the ID column does that now. Its primary purpose is more a redundancy at this point I guess.
There was a problem hiding this comment.
I think you should mention that this one is autogenerated, not configurable
| @@ -0,0 +1,75 @@ | |||
| # PSCID (Project Study Center ID) | |||
There was a problem hiding this comment.
File name shoul be all caps too be consistent with how we use it.
| @@ -0,0 +1,75 @@ | |||
| # PSCID (Project Study Center ID) | |||
|
|
|||
| The PSCID is the main participant identifier in Loris. With one ID assigned to each participant per project. It serves the purposes of this this this and this. | |||
There was a problem hiding this comment.
technically not per project but per instance, if you are thinking of CBIG, we just know there are project overlaps and have a system to merge these participants.
There was a problem hiding this comment.
oh and I love the purpose
| |sequential|MTL0006, MTL0007, MTL0008|Generates a static prefix with incrementing numbers| | ||
| |manual|A1, B2, Q5|Generates a fixed-length alphanumeric pattern| | ||
| |random|BUDDY29, BUDDY02, BUDDY96|Generates a static prefix followed by a random number of fixed length| |
There was a problem hiding this comment.
you are mixing generation type with format. i.e. sequential doesnt mean that ther eis a static prefix, thats an option the ADMIN makes, if they choose to have a static section then the config should clearly indicate it and this table doesnt because you are not showing the configuration associated with the example. I think you are better off removing this table and just relying on the content below it that explains it more clearly.
as for the "manual" part, well its manual, nothing gets generated.
| minimum `min` and maximum `max` values for sequentially and randomly generated PSCIDs. | ||
| By default sequence will start at the lowest possible values (i.e.: 0000, AAAA). | ||
|
|
||
| ## Interaction With LORIS |
There was a problem hiding this comment.
Not sure why this section was completely removed from the documentation. its pretty important
|
As per Dave, this should be rebased to main branch |
3 participants
Brief summary of changes
Pscid.mdfile is an example of how this approach could be structured.