Web Client: Parent/Guardian Field vs Secondary Identification
Bug #1714070 reported by
Terran McCanna
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
In 2.12.4:
The field we all know and love as Parent/Guardian in the xul client is called Secondary Identification in the web client (and called ID2 in the patron summary bar).
We currently make heavy use of the Parent/Guardian field - we could just customize the label locally, but it seemed like a good time to bring up this issue of whether Parent/Guardian should be split out to a different field or if Secondary Identification should be relabeled as Parent/Guardian.
Related bugs:
https:/
https:/
https:/
Changed in evergreen: | |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
status: | New → In Progress |
Changed in evergreen: | |
assignee: | nobody → Jason Etheridge (phasefx) |
Changed in evergreen: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In our case, we prefer to keep the ident_type2 as a generic field where libraries can store a variety of different identification types. In the case where staff want to identify a parent/guardian, we encourage them to do so by putting something in the field along with the name noting that it is a parent's name. However, including the parent/guardian in the patron record isn't something done very often here.
Given that we have academic and special libraries in our consortia, it seems odd to those libraries to see a parent/guardian field, especially since this field was identified as ID2 in the patron summary bar. A more generic secondary identification field gives those libraries the flexibility to store something different here (e.g. student id) while also allowing the use of the field for parent/guardian information for those who need it.
Splitting the parent/guardian information out into a different field would also be good as long as it includes a setting to allow it to be hidden for those who don't use it.