eXtensibleCatalog / test

Testing
MIT License
0 stars 0 forks source link

What to do when no NCIP response - microform example #128

Closed patrickzurek closed 7 years ago

patrickzurek commented 7 years ago

JIRA issue created by: rcook Originally opened: 2011-10-28 06:32 PM

Issue body: (nt)

This issue has attachments associated with it (external link): 951-email-alert-turn-on-case1.png 951-email-alert-turn-on-case2.png 951-nciptable.png english.png english2.png microform.png microform2.png ncipdown1.png [ncipdown2 errors.png](http://www.carli.illinois.edu/sites/files/XC_attachments/Drupal-Toolkit/ncipdown2 errors.png) [ncipdown3 general.png](http://www.carli.illinois.edu/sites/files/XC_attachments/Drupal-Toolkit/ncipdown3 general.png) ncipdown4.png

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-10-28 06:38 PM

Comment body:

If there is no NCIP response (as is the case when we have no item records for many of Rochester's microform holdings), then the location data and call number from the Holdings record should be displayed instead. We should still display "Availability unknown" in the full record. On the search results page we should show the same "Unknown" for availability (as opposed to currently showing Not Available) and the call number can come from the holdings record.- is that true Jennifer?

Jennifer and Dave, what do we do if say there is no response from NCIP (for whatever reason) and there is no holdings record?

patrickzurek commented 7 years ago

JIRA Comment by user: dlindahl JIRA Timestamp: 2011-10-29 07:33 PM

Comment body:

Randy, 951 and 952 need to be merged. 952 is about a bug, but the resolution is the same as this, we need to decide WHAT to display in order to fix both issues.

patrickzurek commented 7 years ago

JIRA Comment by user: pkiraly JIRA Timestamp: 2011-11-04 07:58 PM

Comment body:

The current solution is to not showing anything about the availability, only the location and call number. The label of the row became "location:" instead of "availability:". Let me know if you think we should not change the label.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-11-07 09:53 PM

Comment body:

Jennifer and Dave, See newest screen shots or conduct a search of your own. Do you approve of this?

patrickzurek commented 7 years ago

JIRA Comment by user: dlindahl JIRA Timestamp: 2011-11-11 06:07 PM

Comment body:

No I definitely do NOT like this. Ideally we could decide to make a change before we implement it, and not after.

I cannot answer the question without first asking a question.

Do we always have a location available for every result? In the very first screen shot posted in this issue, the Civil Government result shows no location.

If the answer is no, then there are four cases: 1) we have both location and availability to display 2) we have location and no availability 3) we have availability and no location (as in the civil government screen shot) 4) we have neither location, nor availability

I notice that we have a facet called "Library," so that means that we are referring to the location as a "Library" on the left side of the screen and we are referring to a location as "availability" or "location" on the right side of the screen.

In the end, we will probably change the "Library" facet and call it the "Location" facet, we will replace the "Availability" label with "Location" and we will reorder the values in case #1 above, so that the location comes before the availability

Cases 1) "Location: Rhees Stacks - available" 2) "Location: Rhees Stacks" 3) (not sure if this case is possible, or how it could be) 4) (here we do not show anything)

Peter, please do not change anything yet, this is just a discussion at this point.

patrickzurek commented 7 years ago

JIRA Comment by user: jbowen JIRA Timestamp: 2011-11-11 06:33 PM

Comment body:

Just to confirm: Dave's 3rd option (availability but no location) is not possible - in the Civil Government example we had the location but it was not displaying. It is now displaying.

Sounds like Dave is saying we should not have a separate line for availability but put it on the same line as the location - this definitely looks better. Then we don't have to say "Availability: available". Kind of redundant. That might be an improvement.

One more response to Dave: the Library facet is much broader and less specific than Location - they are not the same thing. Hundreds of locations may display under one Library. Whether or not this distinction is meaningful to users is another question

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-11-14 08:10 PM

Comment body:

Peter, there are some changes outlined in this docushare document.

http://docushare.lib.rochester.edu/docushare/dsweb/View/Collection-6878

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-11-21 06:14 PM

Comment body:

I asked Patrick to stop Tomcat to similate NCIP being down and how DT handles it. As you can see form the attached, there are many errors that show. The goal here was to provide urgent emergency notification to the admin, you, so we have to see if that worked but to minimize the impact in the UI. These errors should not show.

Also in the ncipdown2 error screen shot below, you show show the info you have from the holding record as a stand in for what you don't get from the NCIP response, just like you do on the SERP.

patrickzurek commented 7 years ago

JIRA Comment by user: jbowen JIRA Timestamp: 2011-11-22 06:12 PM

Comment body:

I am still seeing the message, "NCIP 0.5.4 test" with "availability unknown) as the status in some cases - I am not logged into the demo site.

http://128.174.70.254/dtmilestone3/?q=node/2244830&hit=10&caller=xc-search

patrickzurek commented 7 years ago

JIRA Comment by user: pkiraly JIRA Timestamp: 2011-11-22 08:09 PM

Comment body:

I created a form, when the site admin can turn on the alerting functionality. The form reflects the current state of the flag, so it no action needed, the admin do not see the button.

First case: the site admin has not been recently alerted


Second case: the site admin has been alerted recently, and he have to turn on alert again