SPARCRequest Wiki

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Meeting:

SPARC OS Technical Committee

Date:

Time:

2:00 pm

MUSC

Iowa

LA CaTS

Children’s National

Case Western

OHSU

Stony Brook Medicine

Morehouse

Agenda

Discussion:

  • SPARCReport permissions - limiting data access per in SPARCCatalog structure.

Institutional Updates:

Louisiana Clinical & Translational Science Center: 

1/17/2024

  • not in attendance

2/14/2024


MUSC:

1/17/2024

  • Released SPARC v3.12.0 (Dec 14th) and v3.12.1 (Jan 10th). Both releases available to OS Community - see blog

  • Working on SPARCFulfillment planned deployment March 21st.

  • SPARC Ruby & Ruby Rails upgrades happening as Fulfillment work being done.

  • OS Governance Dec 11th meeting reviewed MOU demo and is ok with including as a SPARC, customizable feature. Next step is a story describing the work.

2/14/2024

  • Working on SPARCFulfillment planned deployment March 21st

  • SPARC Ruby & Ruby Rails upgrades simultaneous to Fulfillment - tentative deployment end of March 2024, then will work on next SPARC Release


Oregon Health & Science University:

1/17/2024

  • Working on upgrade

2/14/2024


Iowa

1/17/2024

  • not in attendance

2/14/2024


Case Western

1/17/2024

  • Still working toward upgrading to SPARC 3.11.0. Current issue is that ldap isnt going to their institutional login page. Andrew was able to join to give some guidance that ldap is used for adding user to studies, not to present a login page He gave some code base location Jeremy should look at:

    • config/initializers/devise.rb, line 41

    • They may need to use https://github.com/omniauth/omniauth-ldap gem for authentication.

    • config/cas.yml file is a part of code base and a part of v3.11. This is a config file to read db so no need to add to settings.

  • Asked if giving access to Reports allows users to run reports on all SPARC services or only those they can access. His testing showed global access. This should limit to only what they can access, so he’ll check permissions for other access like Super User or Overlord rights. Brigette will do some testing as well to confirm behavior.

    • Post meeting, testing shows SPARC design where being a super user at any Org level lets you have access to SPARCReports with ability to run reports for all. Worth a discussion to see if this should be limited, similarly to how SPARCForms limits to surveys and forms particular to orgs/services.

2/14/2024


Children’s National

1/17/2024

  • not in attendance

2/14/2024


Stony Brook:

1/17/2024

  • not in attendance

2/14/2024


Morehouse:

1/17/2024

  • They are picking SPARC back up for implementation and will reach out with any questions.

2/14/2024

  • No labels