[Koha-cvs] koha/koha-tmpl/intranet-tmpl/npl/en/help/bull s... [rel_2_2]

[Owen Leonard]

CVSROOT:        /sources/koha
Module name:    koha
Branch:         rel_2_2
Changes by:     Owen Leonard <oleonard> 06/09/26 12:59:17

Modified files:
        koha-tmpl/intranet-tmpl/npl/en/help/bull: statecollection.tmpl 

Log message:
        Synching with default template: improved help information for 
subscriptions

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/npl/en/help/bull/statecollection.tmpl?cvsroot=koha&only_with_tag=rel_2_2&r1=1.1.2.2&r2=1.1.2.3

Patches:
Index: statecollection.tmpl
===================================================================
RCS file: 
/sources/koha/koha/koha-tmpl/intranet-tmpl/npl/en/help/bull/Attic/statecollection.tmpl,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -b -r1.1.2.2 -r1.1.2.3
--- statecollection.tmpl        20 May 2006 22:32:39 -0000      1.1.2.2
+++ statecollection.tmpl        26 Sep 2006 12:59:17 -0000      1.1.2.3
@@ -2,26 +2,28 @@
 <div id="main-compact">
        <h1>Serials issues and summary</h1>
        <p>This screen is divided in 2 parts</p>
-       <h2>The right part</h2>
-       <p>The right part deals with issues. When you create a new 
subscription, the 1st issue is automatically calculated. When you want/need, 
you can define issues that have a new status:</p>
+       <h2>The first part, Awaited or Late Subscription Issues</h2>
+       <p>The right part deals with issues. When you create a new 
subscription, the first issue is automatically calculated. When you want/need, 
you can define issues that have a new status:</p>
        <ul>
-               <li>Arrived : when an book arrives, you can set it's status to 
"arrived". Then, the issue disappear from this list, and the number of the 
issue is added to the "arrived list" (on the left box)</li>
-               <li>Late : means that the book is late and should be arrived. A 
books changed to "late" status stays on the issue list, and the next waited 
number is generated</li>
-               <li>Missing : means the book will never arrive. The issue 
disappear from the list, and the number of the issue is added to the "missing 
list" (on the left box)</li>
+               <li><strong>Arrived</strong>: when an book arrives, you can set 
it's status to "arrived". Then, the issue disappear from this list, and the 
number of the issue is added to the "arrived list" (on the left box)</li>
+               <li><strong>Late</strong>: means that the book is late and 
should be arrived. A books changed to "late" status stays on the issue list, 
and the next waited number is generated</li>
+               <li><strong>Missing</strong>: means the book is not in the 
library but has been published (the library's copy has been lost, for example). 
The issue disappear from the list, and the number of the issue is added to the 
"missing list" (in the second box)</li>
        </ul>
-       <h2>The left part</h2>
-       <p>the left part contains 6 differents informations, that are 
automatically calculated for some of them, but that you can change<p>
+<p>When you change an "awaited" issue to something else, the next awaited 
issue is automatically calculated. The issue list contains only awaited/late 
issues and the last five issues.</p>
+       <p><strong>Published on and planned for</strong>: for new issues, those 
values are automatically calculated. The first one is the published date. It is 
usually never modified. The second one is the date where you expect to receive 
the issue or have received it. Late issues depends on planned dates, while the 
published date is useful to order issues in serials summary: for a monthly 
issue, you can receive the february issue in april, but still need to know that 
the february issue has been published before the march one.</p>
+       <h2>The second part</h2>
+       <p>The second part contains six different pieces of information, that 
are automatically calculated for some of them, but that you can change<p>
        <ul>
-               <li>Subscription beginning date : the date of the beginning of 
the 1st subscription. Should not be modified and is not modified automatically 
by subscriptions renewals</li>
-               <li>Subscription enddate : must be entered manually when the 
subscription is definetly closed</li>
-               <li>Arrived numbers : the list of issues you have in your 
library. Automatically filled when a new number is marked "arrived". You can 
manually change this field if you want, for example, to change a long list 
(1,2,3,4,...,51) to a shorter one (1-51)</li>
-               <li>Missing numbers : the list of issues you don't have in your 
library, and that will never arrive (or have been lost). Automatically filled 
when a new number is marked "missing". You can manually change this field if 
you want, for example, to change a long list (1,2,3,4,...,51) to a shorter one 
(1-51)</li>
-               <li>opac note : the field that appears in the OPAC (with some 
other subscription information like beginning date and end date. This field 
must be filled manually. Nothing is put here automatically</li>
-               <li>opac note : the field that appears in the librarian 
interface (with some other subscription information like beginning date and end 
date. This field must be filled manually. Nothing is put here 
automatically.</li>
+               <li>Subscription beginning date: the date of the beginning of 
the first subscription. Should not be modified and is not modified 
automatically by subscriptions renewals</li>
+               <li>Subscription end date: must be entered manually when the 
subscription is definitely closed</li>
+               <li>Arrived numbers: the list of issues you have in your 
library. Automatically filled when a new number is marked "arrived". You can 
manually change this field if you want, for example, to change a long list 
(1,2,3,4,...,51) to a shorter one (1-51)</li>
+               <li>Missing numbers: the list of issues you don't have in your 
library, and that will never arrive (or have been lost). Automatically filled 
when a new number is marked "missing". You can manually change this field if 
you want, for example, to change a long list (1,2,3,4,...,51) to a shorter one 
(1-51)</li>
+               <li>OPAC note: the field that appears in the OPAC (with some 
other subscription information like beginning date and end date. This field 
must be filled manually. Nothing is put here automatically</li>
+               <li>OPAC note: the field that appears in the librarian 
interface (with some other subscription information like beginning date and end 
date. This field must be filled manually. Nothing is put here 
automatically.</li>
        </ul>
        <h2>Subscription renewals</h2>
        <p>Koha calculates automatically the end of the subscription (based on 
the start date and the number of issues received). when a subscription has 
ended, you can't change the status of the last "waited number" (as it's not 
waited in fact). To be able to "receive" this number, you must renew your 
subscription.</p>
-       <p>Renewing a subscription means that you define some informations for 
the renewal. When those informations have been filled, a suggestion is 
automatically created in Koha. This suggestion can be managed by the librarian 
that orders books, as any other order (= budget and bookseller are defined 
here).</p>
+       <p>Renewing a subscription means that you define some information for 
the renewal. When that information has been filled, a suggestion is 
automatically created in Koha. This suggestion can be managed by the librarian 
that orders books, as any other order (= budget and bookseller are defined 
here).</p>
        <p><i>Note that the subscription renewal done by the "serials 
librarian" is supposed to be immediate. We have decided to keep Koha as simple 
as possible. In fact, the subscription renewal won't be immediate, but we 
didn't wanted to add too much complexity.</i></p>
        </p>