serials: "do not use record entry" summary method does not display correctly in tpac

[Kathy Lussier]

Evergreen version 2.2.3

Evergreen provides four options for summary methods in serials: add to record entry, merge with record entry, use record entry only, and do not use record entry.

"Add to record entry" is the default and will display the automatically-generated serials holdings information along with any textual holdings statements added to the 866 field.

"Use record entry" removes the automatically-generated holdings summary and only displays the textual holdings statement from the 866 field. (there is a minor display issue here as reported in bug 1001305).

The "do not use record entry" option has no impact on the tpac display. The holdings summary continues to display as if we were using the "add to record entry" option instead of removing the textual holdings statement as expected.

Also, I'm not sure if the "merge record entry" option is working with tpac yet. A basic test on my end didn't show any difference, but I don't think I have the MFHD holdings statement entered correctly to test this.

[Remington Steed (rjs7)]

I cannot reproduce this bug. The "do not use record entry" option correctly hides the 866 for me in the TPAC. Is it still an issue for you? If so, could you provide more data, including your MFHD record?

[Erica Rohlfs (erohlfs)]

Like Remington, I cannot reproduce this bug. I tested in version 2.5.3b. The "Do not use record entry" is correctly displaying the Evergreen generated holdings statement from the serial control received issues for me without displaying the legacy / MFHD record. Perhaps the issue was fixed in a version between 2.2.3 and 2.5.

[Kathy Lussier (klussier)]

Thank you for looking at this Remington and Erica!

I tested this again today on a 2.5 system and on recent master system with the same results. I was concerned local tpac customizations may have affected my results, so I did a little more testing on the 2.6 community server.

My results initially appeared to be inconsistent, but I think I've narrowed down the problem. If the textual statement is the first one in the record (i.e. when I select "Edit MFHD record" from the "Actions for this record" menu, (1) follows the name of the owning org unit) the system does indeed hide the 866 field when "do not use record entry" is selected. However, if that textual statement is not the first one on the record, then it doesn't work.

Going a little further, the "Add to record" entry and "merge record entry" options also do not display as intended and the only option that does work correctly is "use record entry only." With the first statement, all of the holdings information (both textual and the automatically-generated statements) displays together under the same heading. Once you go beyond the first textual statement, the catalog seems to treat that statement as a separate holdings statement that has nothing to do with the automatically-generated summary belong to the same OU.

This means the summary methods won't work correctly in the following situations:

* When the textual statement has been added after the serials distribution has already been created.
* When there is more than one org unit with holdings on that serial's record (this is the case with the majority of serials records in our system)
* When a textual statement is deleted, and staff at then create a new one.
* Even when the textual statement is added before the serials distribution is created, I found instances where the textual statement suddenly changed to #2. This was inconsistent, and I couldn't pinpoint which sequence of steps would make that number change.

http://demo.evergreencatalog.com/eg/opac/record/1117 is a record on the demo system where I created two identical MFHD records. The one for BR1 is the first MFHD and correctly suppresses the display of the textual statement. The one for BR2 is the third MFHD and is not suppressed. In both cases, the summary method has been set to "do not use record entry."

I don't know how often the database is refreshed on the demo system, so I'll add some screenshots below.

Both subscriptions set to "do not use record entry:"
http://www.screencast.com/t/CcQDpcqVQew

Both subscriptions set to "merge with record entry:"
http://www.screencast.com/t/qoDYy0pLJI

Both subscriptions set to "add to record entry:"
http://www.screencast.com/t/6ZgulJeR

[Kathy Lussier (klussier)]

Ooh! I figured it out after submitting the last comment. We weren't setting the "Legacy Record Entry" field. It works now. Sorry for the noise!