Comment 24 for bug 1691269

Also, going forward, templates need to be fully exportable and importable
from within the web client, without having to maintain a XUL staff client
for every update of the web client.

J. Elaine Hardy
PINES & Collaborative Projects Manager
Georgia Public Library Service/PINES
1800 Century Place, Ste. 150
Atlanta, GA 30045

404.235.7128 Office
404.548.4241 Cell
404.235.7201 FAX

On Thu, Nov 16, 2017 at 7:23 PM, Jason Boyer <email address hidden>
wrote:

> It's possible since the conversion is self-contained in a single
> function. But since I was at the discussion and heard how early days
> that project is I'm not so inclined at all. This needs to be in 3.X as
> soon as possible (ideally 3.0.2 or .3) since catalogers don't give the
> web client a second thought once they hear that all of their templates
> are gone (and have to be remade on every machine they use).
>
> Since there's only one other function that needs changed to determine
> what "remote" means with respect to remote storage in this instance, I
> think it would be more beneficial for staff to get this in ASAP and then
> work out the migration path when there's actually somewhere else to put
> them.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1691269
>
> Title:
> web client: copy templates created on XUL not displayed
>
> Status in Evergreen:
> New
>
> Bug description:
> Copy templates created via Copy Editor on XUL clients are not listed
> on the Web client when creating/editing an item.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1691269/+subscriptions
>