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
Based on the current workflow of the dynamic routing project, it can be hard to know the full rig_id of rig metadata. When fetching the rig metadata from the api we query slims based on ReferenceData name which also happens to be rig_id.
It would be nice if we could fetch rig metadata from this service using a partial rig_id.
This is appears to be a feature that slims can support so I think this is a feature the api can support:
The aind_slims_api snippet attached to this issue doesn't sufficiently address some edgecases (ex: 323_EPHYS1_OPTO_2024-06-18_tube can be matched instead of 323_EPHYS1_OPTO_20240212). This feature may still be supportable (the query might not be as easy). Since there are still discussions on whether or not rig metadata will be stored in slims, I will update the snippet when we have more clarity.
Based on the current workflow of the dynamic routing project, it can be hard to know the full rig_id of rig metadata. When fetching the rig metadata from the api we query slims based on ReferenceData name which also happens to be rig_id.
It would be nice if we could fetch rig metadata from this service using a partial rig_id.
This is appears to be a feature that slims can support so I think this is a feature the api can support:
The text was updated successfully, but these errors were encountered: