Person Data Model
A Person entry provides detailed information about individuals involved in research projects, including their affiliations, roles, and contributions. Accurate person records are essential for tracking collaborations, grant participation, working group involvement, and expertise within scientific initiatives.
This section outlines how to create a valid person entry, ensuring that all necessary details are captured to support identification, categorization, and data integration within MC2 Center-supported projects.
Why You Should Contribute Person Entries¶
Contributing person entries enhances collaboration by providing clear visibility into expertise, roles, and project involvement within research teams. It helps connect researchers and contributors across projects, facilitates networking opportunities, and allows stakeholders to easily identify key personnel for collaboration or consultation. Maintaining up-to-date profiles also supports transparency and improves recognition of contributions to research initiatives.
Who Should Be Contributing Person Entries?¶
- Researchers and Scientists – Document your roles, publications, and collaborations to increase visibility within your field and enable others to reach out for partnerships.
- Project Leads and Investigators – Ensure key contributors to your projects are credited and easily searchable for collaboration and reporting purposes.
- Research Administrators – Keep records of team members, roles, and working group participation to manage projects efficiently and facilitate compliance reporting.
- Consortium Members – Share your expertise and involvement across multiple projects or institutions to encourage cross-disciplinary collaboration and integration of research efforts.
- Data Managers – Link researchers to datasets, tools, and resources they have contributed to ensure traceability and acknowledgment of contributions.
How to Contribute Person Entries¶
To submit a Person entry, complete the Person Entry Submission Form. The MC2 Center will review submissions, collect necessary consent, and curate PersonView entries accordingly.
Example Data Entry¶
The table below includes sample values to demonstrate proper attribute usage.
| Attribute | Example Value |
|---|---|
| Name | Dr. Jane Smith |
| Alternative Names | Jane Doe, J. Smith |
| janesmith@example.com | |
| Url | Professional Profile |
| Orcid Id | 0000-0002-1825-0097 |
| Synapse Profile Id | SP98765432 |
| Last Known Institution | Stanford University |
| Working Group Participation | Cancer Metabolism, Genomic Data Integration |
| Chair Roles | Steering Committee, Ethics Review Panel |
| Consent For Portal Display | Yes |
| Portal Display | TRUE |
| Person View | Public Profile View |
| Person Grant Number | CA202177, CA304599 |
| Person Consortium Name | HTAN, PDMC |
| Person Publications | 25700473, 31245678 |
| Person Datasets | GSE12345, DOI:10.1000/sampledataset |
| Person Tools | R Studio, Python, Jupyter Notebook |
| Person Educational Resources | Advanced Cancer Research Training, NIH Data Science Workshop |
| PersonView_id | PersonView_12345 |
Full Field Reference¶
Below is the full field reference table with attributes and their descriptions.
| Attribute | Description | Required | Validation Rules | Examples |
|---|---|---|---|---|
| Name | Name of the individual | True | None | John Doe |
| Alternative Names | Other ways the individual's name is displayed. Multiple values permitted, comma separated. | False | list like | Bob, Bobby, Robert |
| Email address of the individual | False | None | johndoe@example.com | |
| Url | URL, e.g., individual's home page address | False | None | https://www.google.com |
| Orcid Id | Unique identifier (ORCID ID) of the individual | False | regex search \d{4}-\d{4}-\d{4}-\d{3}(\d|X) | 0000-0002-1825-0097 |
| Synapse Profile Id | Unique identifier (Synapse Profile ID) of the individual. See identifer in the url of the synapse profile page. | False | unique | SP12345678 |
| Last Known Institution | Last known institutional affiliation of the individual. | True | None | Harvard University |
| Working Group Participation | CSBC/PSON working group(s) of which the individual is a member (current and former). Multiple values permitted, comma separated. | True | list like | Cell and Tissue Mechanics |
| Chair Roles | Committee or working group chair role(s) the individual fulfilled (current and former). Multiple values permitted, comma separated. | True | list like | Steering Committee |
| Consent For Portal Display | Consent from individual to display Person information in the CCKP | True | None | Yes |
| Portal Display | Display content in CCKP | True | None | TRUE |
| Person View | The denormalized manifest for person submission. | False | None | Public Profile View |
| Person Grant Number | Grant number(s) associated with the person. Multiple values permitted, comma separated. | True | list like | CA202177 |
| Person Consortium Name | Consortium(s) associated with the person. Multiple values permitted, comma separated. | True | list like | PDMC |
| Person Publications | A list of the pubmed Ids associated with the person. Multiple values permitted, comma separated. | False | list like | 23761710,23761712,23762511 |
| Person Datasets | A list of the dataset aliases (An alias of the dataset must be unique. Can be the GEO identifier such as GSE12345, or a DOI. No Greek Letters) associated with the person. Multiple values permitted, comma separated. | False | list like | GSE12345 |
| Person Tools | A list of the tool names associated with the person. Multiple values permitted, comma separated. | False | list like | CCKP_Tool_456, CCKP_Tool_789 |
| Person Educational Resources | A list of educational resource identifiers associated with the person. Multiple values permitted, comma separated. | False | list like | Nan |
| PersonView_id | A unique primary key that enables record updates using schematic. | True | unique | 23761710 |