SPIKE: StagingDirector TCP/IP & EMS TCP/IP overlap and estimation

Hi. I don’t see linked to this ticket. I think it should be?

Hi   and ,
As already communicated in slack but reposting the estimates -

For the existing commands ramification the ball park estimate for each command would be S/M t-shirt size with LOC of 70%.
1.Inventory Add (IA) - M
2.Pick Request(PR) - M
3.Status Check Message(SC) - S
4.Transaction Response(TR)  - S
5.Heart Beat(HM) - No change
6.Status Message(SM) command - S

For the new command 

1.Inventory delete (ID) - Out of scope

2. Expected Store (ES) - LOC 60% - XL.

With this I conclude the spike and looks like we have kind of got an idea of work involved. But questions may arise during the work and then we can have dedicated calls.

Adding the chat details in the Jira for everyone's visibility ----

One more question I have is for the new commands that are not yet implemented in edge-dematic to determine its estimates we will need more details for it
14 replies

 Also sent to the group

Stephanie Buck  12 days ago

What kind of details do you need?

Gurleen Kaur  12 days ago

I have mentioned in the jira

Gurleen Kaur  11 days ago

Hi @StephB,
Basically we need more details about 2 commands that are listed in the EMS 9.8 document and are not implemented in edge-dematic or mod-remotestorage.
1.Inventory Delete (ID)
2.Expected Store (ES).
Is this the part of deaccession ? because as of now the accession queue operations are in place to work. If these commands are to be made to work then the scope expands and will at least become an XL or XXL work (LOC-60% - 70%) provided we have all the understanding that we have for deaccession.For the existing commands ramification the ball park estimate for each command would be S/M t-shirt size with LOC of 70%.
1.Inventory Add (IA) - M
2.Pick Request(PR) - M
3.Status Check Message(SC) - S
4.Transaction Response(TR)  - S
5.Heart Beat(HM) - No change
6.Status Message(SM) command - S
CC: @Irina Pokhylets

Stephanie Buck  11 days ago

Hi @Gurleen Kaur and others. I'm sorry - I'm working against some hard deadlines for tomorrow on multiple tasks. I'll come back to this as soon as I can.
!https://a.slack-edge.com/production-standard-emoji-assets/14.0/google-small/2705@2x.png!1
 

Stephanie Buck  10 days ago

Working on this today and Monday (edited) 

Stephanie Buck  5 days ago

Hi @Gurleen Kaur. Thanks for your patience. I have updated the ticket with what I've learned. I'll copy it below as well.Inventory delete (ID) is part of deaccessioning, and can be postponed until deaccessioning as a whole is worked on for remote storage. It is not in scope of this work.
Expected Store is sent from Sierra when an ASRS item is checked in in Sierra. In Sierra, when the item is checked in, Sierra sends the ES message and also sets the item status to ‘in transit’. EMS then sends an Inventory Confirm (IC) message back to Sierra to confirm the item has been stored. Sierra then changes the item status to Available.
Regarding Expected Store (ES), what we are seeing now is that when a Remote Storage item is checked in in FOLIO: * The item status is set to Available, not In Transit.

• When the item is checked in in EMS, EMS sends an Item Returned (IR) message to FOLIO.

Currently, for an item checked out of ASRS, there is no message from FOLIO to EMS about an item to be returned back into ASRS and there should be. This message is in scope.

Gurleen Kaur  5 days ago

Thanks @StephB, I shall take a look at the above stated requirement.
I hope you are doing well too,

Stephanie Buck  5 days ago

Thank you, Gurleen. I'm feeling better each day.

Gurleen Kaur  4 days ago

Hi @StephB,
I am still trying to understand the scope of work for Expected Store (ES)  message.Please correct me if I am wrong - # ES message is it part of any flow Accession or Retrieval flow (maybe not)?

1. When a check out action is performed in FOLIO for an ASRS item (which means an item that is having its permanent or effective location as a remote location) then an ES message will be triggered from FOLIO i.e from staging director for this item?

2. Who will listen to this message and process it ?

(edited)

Stephanie Buck  4 days ago

1. ES is part of circulation - so accession and someone returning an item that has been checked out to a patron.

2. Verifying - I think the messages need to be send when an item is checked in to FOLIO - "we should have the Expected Store message sent from FOLIO when a Remote Storage item is checked in in FOLIO using the Remote Storage service point"

3. EMS - the remote storage system

I've forwarded the email thread to you so you can see all of the messages, and maybe have more context. (edited) 

Gurleen Kaur  3 days ago

Thanks @StephB,
I went through the mail, yes I think at check-in we need to sent the ES message from folio. I think in that case another queue is required apart from existing accession and retrieval queue maybe called expected store queue perhaps..
Accession and retrieval flows initiated by Folio – at the configurable interval edge-dematic checks two queues: accession queue and retrieval queue (filled by `mod-remote-storage` when circulation events occur). If new records are present, module sends requests to SD via primary channel. SD then sends responses or, in case of item return, a return message via status channel.
If my understanding above is correct and we have to place it another dedicated queue for ES then efforts will grow and probably would be an XL tshirt size implementation. (edited) 

Stephanie Buck  3 days ago

Hi @Gurleen Kaur. I think we should try to get a call set up. I don't know that I'm following what queue means in this context. Since we close the sprint today/Monday, can you leave your estimates and reasoning in the ticket? If you feel like you've completed the ask in the ticket, it can be closed.

Gurleen Kaur  3 days ago

Sure I can leave my comments on the jira and yes pretty much I have got an idea of the work but maybe more questions will erupt when the actual work will be done maybe then we can have dedicated calls for it ?

Stephanie Buck  3 days ago

That sounds good. Thank you very much for your time and effort here!
!https://a.slack-edge.com/production-standard-emoji-assets/14.0/google-small/1f44d@2x.png!1
 

Hello , 
Added you in the ongoing chat. Please check if you are able to view the messages.

- Is that a restricted conversation? I don't see any content when I click the link.