Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please create a repo project for the OMOP subgroup. #255

Open
barabo opened this issue Aug 6, 2024 · 5 comments
Open

Please create a repo project for the OMOP subgroup. #255

barabo opened this issue Aug 6, 2024 · 5 comments
Assignees
Labels
OMOP Issues relating to OMOP on SQL on FHIR

Comments

@barabo
Copy link
Contributor

barabo commented Aug 6, 2024

After the WG call on 2024-08-06, we discussed exploring the idea of using a GH repo project to manage the group effort for the OMOP subgroup (the Parquet subgroup is welcome to do the same for their subgroup-specific discussions and issues).

Can one of the repo owners please create an OMOP project and add me to it?

@arjun
Copy link
Collaborator

arjun commented Aug 6, 2024

@niquola I think you have the rights to do this under the GH "FHIR organization" but I don't.

I agree we should have a GH project for both the OMOP and Parquet subgroups

@arjun
Copy link
Collaborator

arjun commented Aug 6, 2024

I believe the "new project" link should be here: https://github.com/orgs/FHIR/projects

@johngrimes
Copy link
Collaborator

Do we need a new project? Maybe it is just a new board.

@barabo
Copy link
Contributor Author

barabo commented Aug 9, 2024

I believe a new board in the project would be a different view of the existing items, which would be fine for the new view as long as we can identify a filter for it. Anything we create on the new view would also appear in the existing board, but we could create an inverse filter to remove OMOP items from the main view if it gets cluttered.

Looking at my personal account where I have admin access to projects, I see that in the Project settings, I can create custom fields for project items. We could define a 'subgroup' field and use that for OMOP / Parquet specific things.

image

@arjun
Copy link
Collaborator

arjun commented Aug 11, 2024

@jmandel Could you help with this (I think you helped with the initial setup of this repo)?

We'd like to setup either:

  1. new board for the OMOP subproject with a custom field to identify related items or possibly
  2. a new OMOP "project". (I think this is the cleaner approach -- but don't grok GithubJIRA :) )

@arjun arjun added the OMOP Issues relating to OMOP on SQL on FHIR label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OMOP Issues relating to OMOP on SQL on FHIR
Projects
Status: No status
Development

No branches or pull requests

5 participants