Can't report an issue & Shared instrumentation

13 views
Skip to first unread message

Jaclyn Kalmar

unread,
Dec 7, 2020, 4:34:16 PM12/7/20
to CHORUS Project
Hello!

So I have 2 things.

1. I can't report an issue since I can't fill out the priority section.

2. The issue/improvement I was trying to report is about not being able to re-create an instrument under a new lab as it has been "claimed" by another lab. The physical instrument is shared instrument but the data isn't.

Thanks!

Jackie

Michael MacCoss

unread,
Dec 12, 2020, 2:51:14 AM12/12/20
to Jaclyn Kalmar, CHORUS Project
Hi Jaclyn,
Sorry for the delay in getting back to you. I'm not quite sure I understand what you mean in #1. Your question in #2 is a good point. When we originally came up with the design of Chorus we assumed that the folder in the cloud would mimic the local drive. So if the instrument was shared, the backup in Chorus would be in a common lab. Just like you probably do on the local instrument computer you move the data to separate folders you can do something similar in Chorus. That said I understand the complication. 

It is fine to add the same instrument twice in chorus. You can't have the same serial number twice but you could always add an extra digit to the end to get around this. We don't confirm the authenticity of the serial number with the data. 

I hope this helps. 
Mike 






--
You received this message because you are subscribed to the Google Groups "CHORUS Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chorus-projec...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chorus-project/0c2de970-ab85-4a62-ae72-d9d9d3792420n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages