Wishlist: Standalone client should have options to set default due dates

Bug #1267270 reported by Michele Morgan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Wishlist
Unassigned

Bug Description

The default due dates in the Standalone client in the checkout and renewal screens are hard coded to 14 days. Users can choose different loan periods, but it would be very helpful if libraries could choose their own defaults for checkout and renewal to match their policies and minimize changing the interval for each transaction.

The due dates are hard coded in:

offline_checkout.js
offline_renew.js

as follows:

       var todayPlus = new Date(); todayPlus.setTime( today.getTime() + 24*60*60*1000*14 )

There should be options to set this for a given workstations. Separate checkin and renewal default due dates should be supported for libraries that have different loan periods for renewals as opposed to checkouts.

Revision history for this message
Jason Stephenson (jstephenson) wrote : Re: [Bug 1267270] [NEW] Wishlist: Standalone client should have options to set default due dates

We did this at MVLC by making a custom code branch in our git repository
to change the standalone client's code so that 21 days was the default.
I think we also removed some of the loan periods that our members don't
use and maybe added some to the menu.

Not saying that this bug report is invalid, as it would be nice to
configure the standalone client's menus, just that we solved this
problem with a custom code branch that simply modifies the existing
menus. Making it customizable was deemed to require too much work at the
time we did this.

Since the standalone client almost never changes, we still merge that
branch as-is into our production code base whenever we update. It has
not been rebased in over two years. It hasn't needed it.

Guess what I am trying to say is that this is one place where having a
branch for local code changes has been painless.

Ben Shum (bshum)
Changed in evergreen:
importance: Undecided → Wishlist
status: New → Triaged
tags: added: standalone
Revision history for this message
Jason Boyer (jboyer) wrote :

Now that this is set in a TT2 template does that address the issue at hand or was the desire to make use of an OUS or something similar? The worst aspect of this (choosing a date between each user) is no longer an issue since the web client offline mode doesn't clear the date between users.

tags: added: offline
Revision history for this message
Andrea Neiman (aneiman) wrote :

As Jason Boyer notes, the worst part of this is no longer an issue in the webclient. However I can see where having an OUS or the like to set a default date would be helpful. The question is does that remain on this (mostly XUL-related bug) or is it worth closing this one and opening a new web client-specific bug?

tags: added: wishlist
removed: standalone
Revision history for this message
Terran McCanna (tmccanna) wrote :

I agree that this is no longer the same issue that it once was. I am closing this one, if someone still desires the ability to set a default date via OUS, please create a new wish list bug for the web client version.

Changed in evergreen:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.