Web Client: Location Missing from Item Out

It appears that some other options are also missing from the "Items Out" interface. These include: Acquisition cost, Is Floating, Age Based Hold Protection.

Additionally, Last Edit Date/Time and Record Creation Date/Time display twice in the column picker. In both cases, it looks as though one option refers to the copy and the other to the bib record. These labels should distinguish between the two.

EG 3.0.7

A proposed patch is at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1778083-location-missing-from-items-out

The patch adds Location, Floating Group, and Age-based Hold Protection as column options to the items out grid. I made them hidden by default.

The other fields mentioned in this bug, Edit Date/Time, Record Creation Date/Time, and Acquisition Cost (which actually appears as an option as 'Cost') are pulled into the list of options via a wild card character. These columns are more related to bug #1735808. https://bugs.launchpad.net/evergreen/+bug/1735808

The patch is much appreciated. Can someone explain what is meant by "wild card character." I know what the phrase means, but not in the context of a column picker.

Thank you,
Scott

Hi Scott,

Wildcard character may just be my term. In the grid definitions there are lines with asterisks like the one below.

<eg-grid-field path="target_copy.*" hidden></eg-grid-field>

Instead of defining each field in the drop-down individually, this line pulls definitions for the copy options from the field mapper.

Garry,
  So....this is not something I can do in the staff client. Is this correct?

Scott

Scott,

I'm not sure what you mean by 'this' but it sounds incorrect.

My patch brings in columns from linked tables to which the original code was not making references.

What it doesn't do is rename some labels in the drop-down list, such as Cost, and Last Edit Date/Time, which are already available in the list. This can easily be done if the fields are individually defined in the code, instead of brought in by a wild card. That's what bug #1735808 is about.

When this is done we need to get community support on which columns need to be in the drop-downs and which do not, and there's a sorting issue that needs to be resolved.

But if there are columns that are missing that are needed by staff, I think that's more important than the sorting issue. IMO.

I am testing this patch.

I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>

Pushed to master, rel_3_2, and rel_3_1. Thanks, Garry and Dawn!

Looks like the 3.1 milestone may have been missed for this bug. It's currently pointing at 3.2.1 twice