You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier this month at a hubverse developer’s meeting, we proposed the idea of updating the schema so the next version would require that target keys should contain a single value (i.e. target keys should be represented by a single column). Implementing this change would reduce unnecessary complexity in hub setups. We plan to release this version before the end of January.
To our knowledge, there are no public hubs that use multiple target keys. If you administer a hub that uses multiple target keys, please let me know and we will work with you to find a solution.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
(cross-posted from the hubverse mailing list)
Earlier this month at a hubverse developer’s meeting, we proposed the idea of updating the schema so the next version would require that target keys should contain a single value (i.e. target keys should be represented by a single column). Implementing this change would reduce unnecessary complexity in hub setups. We plan to release this version before the end of January.
To our knowledge, there are no public hubs that use multiple target keys. If you administer a hub that uses multiple target keys, please let me know and we will work with you to find a solution.
Issue in Schemas repository: hubverse-org/schemas#117
Decision record: https://github.com/reichlab/decisions/blob/main/decisions/2024-12-11-ldr-hubverse-target_keys.md
Beta Was this translation helpful? Give feedback.
All reactions