Bug 18379 - Manage e-journals in serials
Summary: Manage e-journals in serials
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Serials (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement with 10 votes (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-04 12:06 UTC by Sunita
Modified: 2020-02-26 07:10 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sunita 2017-04-04 12:06:35 UTC
For renewing ejournals there is only a need of subscription period and no need to add issues. But this feature is not there for renewing ejournals through serials.
Comment 1 Katrin Fischer 2019-05-05 08:56:37 UTC
Can you describe a bit more how you would expect this to work?
Comment 2 Joy Nelson 2020-02-25 22:07:31 UTC
Katrin,
We have had a couple libraries ask about this feature as well.  Below is their explanation of why they would like this functionality.

We are gradually migrating our serials to online-only (e-only) and now have about 100 out of 600 subscriptions as e-only.  We would like to keep these as serials subscriptions and manage these through the serials module, together with our other serials—but the module prompts us to check-in issues.  As we no longer receive print issues, we do not want to receive issues in Koha.  Would there be a way of having an active subscription without checking in issues? 

We proposed (in 2016) this general idea of a development process - although there are many details that would need to be addressed in how Koha uses/displays subscription information in the OPAC/Staff.  It might make more sense to create a new Module in Koha that manages e-resources?  Then again, maybe not!


* Add a new serial type option selector to serials
    -Definable in Authorized Values (print, electronic, mixed)
* Make the numbering pattern optional
  * Will add option for 'no numbering pattern' to pull down
  * Will skip predictor if this is selected
* Add checkbox to subscription editing to show/don't show 'Subscriptions' tab in OPAC
* Add a link to full subscription history to bib details (above holdings table) to the OPAC if subscriptions tab is shown


Hope this helps.  Let me know if you think we should set up an RFC for this development as it does have the potential for a lot of detail.

joy
Comment 3 Katrin Fischer 2020-02-26 07:10:50 UTC
Hi Joy, I think this kind of information is really useful - was never wondering about the why, more about the how! :)

What you list, I think, would even make several good features:

* Add a new serial type option selector to serials
    -Definable in Authorized Values (print, electronic, mixed)

I think something like this could be achieved with the additional subscription fields at the moment. If we want to tie specific functionality to certain types, it might be better to 'harcode' the options. If it's for searching and display, maybe the additional fields already work well enough?


* Make the numbering pattern optional
  * Will add option for 'no numbering pattern' to pull down
  * Will skip predictor if this is selected

Maybe even have a checkbox that deactivates the whole section/fields used for predictions? "Don't predict issues"

* Add checkbox to subscription editing to show/don't show 'Subscriptions' tab in OPAC

I can see this being useful for print as well - sometimes there are subscriptions where the issues are not publicly available, for internal use, staff or even a certain researcher. So this could be generally useful.

* Add a link to full subscription history to bib details (above holdings table) to the OPAC if subscriptions tab is shown

Wondering: I once had a library ask if they could track electronic issues as well. I think the reasoning was that they wanted to inform the researchers of the availability (similar to print) by email. So with the approach above that would work, when we just let libraries decide when to track issues.