|
18 | 18 | Release notes |
19 | 19 | ============= |
20 | 20 |
|
| 21 | +v0.10.0 |
| 22 | +------- |
| 23 | + |
| 24 | +User interface |
| 25 | +-------------- |
| 26 | + |
| 27 | +Public interface |
| 28 | +~~~~~~~~~~~~~~~~ |
| 29 | + |
| 30 | +- Keeps the active tab on the document or person detailed view on page |
| 31 | + reloads. |
| 32 | + |
| 33 | +Professional interface |
| 34 | +~~~~~~~~~~~~~~~~~~~~~~ |
| 35 | + |
| 36 | +- Renders the language menu with the same look as in the public |
| 37 | + interface: |
| 38 | + |
| 39 | + - Uses the same icons. |
| 40 | + - Removes the current language. |
| 41 | + - Avoids to translate the language menu. |
| 42 | + - Adds a divider to separate the language menu from the help link. |
| 43 | + |
| 44 | +- Takes the entire screen width. This is useful for the improvement of |
| 45 | + the editor. |
| 46 | +- Improves the document editor: |
| 47 | + |
| 48 | + - Sets a max width for selects and inputs. |
| 49 | + - Sets bold font weight for titles. |
| 50 | + - Hides fields with unique value (as ``bf:Place``). |
| 51 | + - Displays fields inline and makes this configurable through a HTML class |
| 52 | + in the JSON schema. |
| 53 | + - Adds HTML class in the JSON schema to fix max width and title font |
| 54 | + size. |
| 55 | + |
| 56 | +- Implements interface components to import bibliographic records from |
| 57 | + external sources through the web (SRU protocol). The librarian searches in a |
| 58 | + regular search interface for the desired record, using a simple query |
| 59 | + (keywords for the author, title, date, IDs…), selects a record, gets a |
| 60 | + preview in two formats (the RERO ILS JSON rendered in HTML, and MARC). Once |
| 61 | + the desired record is identified, through an *Import* button, the record is |
| 62 | + loaded into the document editor to be modified and then added to the |
| 63 | + catalog. At this stage, only the BnF SRU service is implemented. |
| 64 | +- Fixes the redirection to the parent document after the deletion of an item. |
| 65 | + This behaviour has been generalized to every parent/child resource |
| 66 | + relationship through a modification in the routing configuration. |
| 67 | +- Allows to receive a serial issue through the professional |
| 68 | + interface (see the acquisition section, below). The workflow begins on the |
| 69 | + holding detailed view and then continues on a dedicated view for serial |
| 70 | + issues. The *Quick receipt* automatically receive a regular issue and create |
| 71 | + the corresponding item. |
| 72 | +- Improves the transaction data displayed on the item detailed view, |
| 73 | + depending on the transaction type (checkout or request), to avoid |
| 74 | + displaying an empty pickup location name when this data is not |
| 75 | + relevant. |
| 76 | + |
| 77 | +Circulation |
| 78 | +----------- |
| 79 | + |
| 80 | +- Adapts the patron profile URL in notification messages to the active RERO |
| 81 | + ILS instance. |
| 82 | +- Adds a CLI for notifications to start the notification process with |
| 83 | + ``invenio run notifications process``. |
| 84 | + |
| 85 | +Metadata |
| 86 | +-------- |
| 87 | + |
| 88 | +- Adds a translation mechanism for the resource editor (documents, items…). |
| 89 | + The translated schemas keys in the `rero-ils` project are served through an |
| 90 | + API endpoint to the `rero-ils-ui` project, in order to avoid translating |
| 91 | + them twice. |
| 92 | +- Holding record, serial pattern: |
| 93 | + |
| 94 | + - Adds a field to describe the publication frequency of a serial pattern. |
| 95 | + The librarian has to pick from a fixed list of 15 frequencies, which |
| 96 | + correspond to the standard RDA list. |
| 97 | + - Adds an ``expected_date_for_first_issue`` field to indicate the expected |
| 98 | + date of the first issue to be received. |
| 99 | + - Sets the ``next_expected_date`` field as required for regular |
| 100 | + frequencies. |
| 101 | + - Adapts the item JSON schema to display fields conditionally. |
| 102 | + |
| 103 | +- Adds ``type`` field in the item record, to distinguish between |
| 104 | + standard item and serial issue. If the item is of type ``issue``, |
| 105 | + then the ``issue`` field is required, to describe the issuance |
| 106 | + details and issue status. Issue items can only be attached to |
| 107 | + holdings of serial type. |
| 108 | + The field ``item_type`` that indicates the circulation category will |
| 109 | + be removed later. The item circulation status is described in the |
| 110 | + ``item.status`` field, while the issue status is described in the |
| 111 | + ``item.issue.status``. |
| 112 | +- Adds ``notes`` field in the item JSON schema. Four types of notes have been |
| 113 | + added, two regarding their audience (public or staff) and two regarding a |
| 114 | + circulation operation (checkin/checkout). The notes are displayed according |
| 115 | + to their type: public notes are publicly displayed on the document detail |
| 116 | + view of the public interface, staff notes are displayed on the same view but |
| 117 | + in the professional interface, checkin notes are displayed as a permanent |
| 118 | + alert as the item is checked in, and checkout notes are displayed as a |
| 119 | + circulation transaction occurs. |
| 120 | +- Uses ``JSONSCHEMAS_REPLACE_REFS = True`` to resolve JSON reference |
| 121 | + before serving the schema. |
| 122 | +- Removes the ``document-minimal-v0.0.1.json`` schema, as it is not |
| 123 | + used. |
| 124 | + |
| 125 | +Acquisition |
| 126 | +----------- |
| 127 | + |
| 128 | +- Receive an issue: |
| 129 | + |
| 130 | + - Allows the librarian to receive new issues through the holdings detailed |
| 131 | + view. The system, based on the holdings pattern, computes the next issue |
| 132 | + pattern and expected date. The librarian is able to add irregular or |
| 133 | + exceptional issues. |
| 134 | + - Updates automatically the ``next_expected_date`` after a successful |
| 135 | + receipt of a regular issue (``expected_date`` of the receipt issue plus |
| 136 | + the pattern frequency). |
| 137 | + |
| 138 | +API |
| 139 | +--- |
| 140 | + |
| 141 | +- Corrects the process used when starting a delayed bulk indexing |
| 142 | + (switch from ``invenio-indexer`` to ``IlsRecordindexer``). |
| 143 | +- Uses the standard JSON schema end point (``/schemas``). |
| 144 | +- Restricts the receipt of issue to librarians of the holdings record's |
| 145 | + library. |
| 146 | +- The pattern preview API returns the ``issue_display_text`` (based on |
| 147 | + the preview template) and the ``expected_date``. |
| 148 | +- The holding API is able to receive the next regular issue. |
| 149 | + |
| 150 | +Documentation |
| 151 | +------------- |
| 152 | + |
| 153 | +- Documents all circulation actions, trying to be the most |
| 154 | + comprehensive in the context of a library network with complex internal |
| 155 | + circulation workflows. Actions, scenarios and chart can be found in |
| 156 | + ```/doc/README.md#circulation`` |
| 157 | + <https://github.com/rero/rero-ils/blob/dev/doc/README.md#circulation>`__. In |
| 158 | + the same move, the babel configuration has been cleaned. |
| 159 | +- Removes unnecessary documentation in the ``LICENSE`` file. |
| 160 | +- Fixes the ``AUTHORS.rst`` file (wrong indentation). |
| 161 | +- Improves the github issue templates to automatically add various labels to |
| 162 | + the issue, depending on the type of issue (bug, correction, enhancement, |
| 163 | + etc.). This should also ease the process of issue creation and triage. |
| 164 | +- Creates an API to expose which roles can be managed by the current |
| 165 | + logged user. Introduces a restriction to prevent the current user to |
| 166 | + delete itself. |
| 167 | + |
| 168 | +Translation |
| 169 | +----------- |
| 170 | + |
| 171 | +- Fixes a wrong rule in the babel configuration that prevented strings |
| 172 | + to be extracted from the document JSON schema. |
| 173 | + |
| 174 | +Instance |
| 175 | +-------- |
| 176 | + |
| 177 | +- Upgrades assets utilities (``clean-css``, ``node-sass``\ …) |
| 178 | +- Fixes version number in the ``pyproject.toml`` file. |
| 179 | +- Uses enabled state of tasks already saved in REDIS. |
| 180 | +- Integrates ``invenio-sip2`` module, that can be installed with a new |
| 181 | + option for the ``bootstrap`` script. |
| 182 | +- The module ``rero-ils-ui`` uses the ``ng-core`` library in version |
| 183 | + ``v0.5.0``. |
| 184 | + |
| 185 | +Scripts |
| 186 | +~~~~~~~ |
| 187 | + |
| 188 | +- Fixes ``server`` script to make use of the correct scheduler backend |
| 189 | + and prevents ``rero_ils.schedulers.RedisScheduler`` file creation. |
| 190 | + |
| 191 | +Fixed issues |
| 192 | +------------ |
| 193 | + |
| 194 | +- `#802 <https://github.com/rero/rero-ils/issues/802>`__: In the |
| 195 | + notification sent to the patron, the patron profile URL isn’t adapted |
| 196 | + to the running RERO ILS instance URL. |
| 197 | +- `#821 <https://github.com/rero/rero-ils/issues/821>`__: The switch |
| 198 | + library menu of the professional interface should be better positioned. The |
| 199 | + menu itself should directly inform the librarian of which library is |
| 200 | + selected. Furthermore, the switch library menu should be displayed on every |
| 201 | + page of the professional interface, not only on the home page. When another |
| 202 | + library is selected, the page is reloaded with the new context, implying a |
| 203 | + possible data loss. |
| 204 | +- `#822 <https://github.com/rero/rero-ils/issues/822>`__: The switch |
| 205 | + library menu of the professional interface is not dynamically |
| 206 | + populated after the creation of a new library. |
| 207 | +- `#930 <https://github.com/rero/rero-ils/issues/930>`__: A librarian |
| 208 | + could edit librarian records of other libraries and manage system |
| 209 | + librarian roles. |
| 210 | +- `#943 <https://github.com/rero/rero-ils/issues/943>`__: Selecting |
| 211 | + another interface language in the professional interface wasn’t |
| 212 | + changing the language of the editor. |
| 213 | +- `#1033 <https://github.com/rero/rero-ils/issues/1033>`__: Restarting |
| 214 | + the scheduler disables entries. |
| 215 | +- `#1036 <https://github.com/rero/rero-ils/issues/1036>`__: ``notes`` |
| 216 | + field prevents to save document record. |
| 217 | +- `#1038 <https://github.com/rero/rero-ils/issues/1038>`__: The person |
| 218 | + selector in the document editor doesn’t display the birth and death dates of |
| 219 | + the person correctly. |
| 220 | + |
| 221 | +Known issues |
| 222 | +------------ |
| 223 | + |
| 224 | +There are some critical issues on the editor, that are known and are |
| 225 | +going to be fixed by one of the next sprints (July 2020 or August 2020): |
| 226 | + |
| 227 | +- `#906 <https://github.com/rero/rero-ils/issues/906>`__: saving a document |
| 228 | + with edition responsibility is not possible. |
| 229 | +- `#1003 <https://github.com/rero/rero-ils/issues/1003>`__: multiple provision |
| 230 | + activity are lost when editing a document. |
| 231 | +- `#1035 <https://github.com/rero/rero-ils/issues/1035>`__: the navigation |
| 232 | + helper (*jump to*) is not always functioning. |
| 233 | + |
| 234 | + |
21 | 235 | v0.9.1 |
22 | 236 | ------ |
23 | 237 |
|
|
0 commit comments