[Pansophy] WMGRDR work CEBAF SAD 2020

[Mike Drury]

Hey Valerie!
I'm doing OK.  Just trying to remember why I haven't retired yet ;)
I think I was referring to Docushare, yes.
I think maybe your second option might work better for these guys as 
long as someone like me and /or Ari could be made aware of updates.
You should be seeing a number of procedures in the next couple of days.  
I'm trying to review some right now.
We may need other help- I'll let you know.
Thanks,
Mike

On 1/13/2021 3:19 PM, Valerie Bookwalter wrote:
>
> Hi Mike!
>
> How are you holding up? Busy busy busy... lol
>
> Thanks for forwarding the emails below. I think you are referring to 
> DocuShare?
>
> If so, then we would need to make sure all the "guys" have accounts to 
> get access to the files.
>
> We would need to know who would need access.
>
> Another possibility would be to have the “official” version in 
> DocuShare with a copy under Pansophy, that way user accounts for 
> DocuShare would not be needed, just log into Pansophy to get to the 
> files. Let me know what works for you.
>
> There is a project directory setup already for WMGRDR work...
>
> https://jlabdoc.jlab.org/docushare/dsweb/View/Collection-49637 
> <https://jlabdoc.jlab.org/docushare/dsweb/View/Collection-49637>
>
> I just showed this to Tony since he was not aware that this area had 
> been set up. Currently, sadly, there are no procedures in place yet.
>
> Please let us know how we can help. We can help write some travelers, 
> look for stuff, train people, help somehow?
>
> Valerie Bookwalter
>
> Jefferson Lab, SRF Department
>
> Pansophy Team
>
> 1-757-813-6716 (CELL)
>
> 1-767-269-5802 (OFFICE – currently working offsite)
>
> ------------------------------------------------------------------------
>
> *From:*Mike Drury <drury at jlab.org>
> *Sent:* Wednesday, January 13, 2021 2:52 PM
> *To:* Camille Ginsburg <ginsburg at jlab.org>; Anthony DiPette 
> <dipette at jlab.org>
> *Cc:* Steve Suhring <suhring at jlab.org>; Valerie Bookwalter 
> <bookwalt at jlab.org>
> *Subject:* Re: procedure in SRF
>
> I think that Pansophy can do notifications of file updates and the like.
> Mike
>
> On 1/13/2021 2:37 PM, Camille Ginsburg wrote:
>
>     Dear Mike, Dear Anthony
>
>     I would hope that once we get past the initial phase in which many
>     corrections or clarifications are needed, that updates would be
>     infrequent.  It would be on the work supervisors to notice or be
>     informed of updates. If we had TeamCenter, the notification could
>     be made automatic.  Just saying.
>
>     Thanks for the feedback.  I'll ask for the procedures to be put in
>     the SRF repository.
>
>     Best wishes,
>
>     Camille
>
>     ------------------------------------------------------------------------
>
>     *From:*Mike Drury <drury at jlab.org> <mailto:drury at jlab.org>
>     *Sent:* Wednesday, January 13, 2021 1:58 PM
>     *To:* Anthony DiPette <dipette at jlab.org>
>     <mailto:dipette at jlab.org>; Camille Ginsburg <ginsburg at jlab.org>
>     <mailto:ginsburg at jlab.org>
>     *Cc:* Steve Suhring <suhring at jlab.org> <mailto:suhring at jlab.org>
>     *Subject:* Re: procedure in SRF
>
>     Its probably a good idea for the techs to have accounts so that
>     they can get at the procedures if necessary.  I'd hope that they
>     would have some sort of a binder downstairs with printouts.  I'll
>     be looking into that in the morning.
>     Its not a particularly difficult system to use.  If we provide
>     links to where the procedures are, then it shouldn't be a big
>     deal.  I'm pretty sure that Frank would have an account and could
>     show the guys how to use.    I can do this as well.
>     I would hope that the procedures aren't constantly evolving and
>     that a set of hard copies would cover the needs in the tunnel.
>     Mike
>
>     On 1/13/2021 1:28 PM, Anthony DiPette wrote:
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20210113/6f77c18d/attachment-0001.html>