Page Comparison

Table of Contents

...

• Inventory items now have a restricted set of valid statuses. Environments which are using their own statuses will need to change their records accordingly. The statuses are as follows (the capitalisation is important):  Available; Awaiting pickup; Awaiting delivery; Checked out; In process; In transit; Missing; On order; Paged; Declared lost; Order closed and Claimed returned.
• Overdue fine policies must be set up and circulation rules have to refer to policies that exist.  If you do not charge overdue fines, you need to create one overdue fine policy that is for an overdue fine of 0 and use that overdue fine policy for every circulation rule.
• Lost item fine policies must be set up and circulation rules have to refer to policies that exist.  If you do not charge lost item fees, you need to create one lost item fee policy that is for a lost item fee of blank and use that lost item fee policy for every circulation rule.  Here is an example of a default Lost Item Fee Policy to use if you do not charge lost item fees.  The one required setting you will need to enter is the For lost items not charged a fee/fine, close the loan after interval.  This setting is needed to insure that the loan is eventually closed.
• Upon deployment make sure that automatic fee/fine types were added to the mod-feesfines database.  Otherwise overdue fine creation functionality will not work for Q1 2020 release and lost item processing will not work for Q2 2020 release. To check, make a call to /feefines?query=automatic==true.  The response should contain 4 entries: "Overdue fine", "Lost item fee", Lost item processing fee" and "Replacement processing fee."
• All Service Points must be associated with a Fee/Fine Owner at Settings>Users>Fee/Fine: Owners for overdue fines to work properly.  If an overdue fine is calculated for an item with an Effective Location whose Primary Service Point is not associated to a Fee/Fine Owner, the overdue fine will NOT be charged to the patron.  (In the future we will have a Default Fee/fine Owner to be charged.  See UXPROD-2278 for details.)
• mod-calendar: History/audit tables (table names starting with audit_) are truncated (all data deleted) on upgrade. The format of the audit tables has been changed in RMB 25.0.0, there is no conversion because RMB versions before 25 were outdated and unsupported in Edelweiss.
• nodejs >= 10.0.0 is required to build the stripes (UI) javascript bundle. Previous releases supported nodejs >= 8.0.0.
• PubSub is being used and required in Fameflower. PubSub module allows use of the event-driven approach in cross-module interactions. This module works on top of Kafka/Zookeeper to deliver messages and create a queue of events. For supporting messaging between modules and correct PubSub mechanism work, it needs to have a Kafka/Zookeeper stack for FOLIO environments. It's important to have the right order on environments setup. First of all, start Kafka, then mod-pub-sub and after it, all other modules with dependencies on PubSub modules.  For more information on installation or verifying that Kafka and PubSub are working together properly, consult the PubSub readme documentation or contact Oleksii Kuzminov Taras Spashchenko.  
• Organizations codes must now be unique. This will prevent the migration of your organization records from Edelweiss to Fameflower if the Code they are using is used by another organization that was migrated first. There is a fix, but it was decided that this can wait until the Q2 release so there will be no Hotfix. A workaround would be making sure you have no duplicate code before the migration begins. JIRA issue 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODORGSTOR-68

• User barcodes must be unique. This includes barcodes which have been set to an empty string. To workaround make sure you have no duplicate barcode before the migration begins.

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUSERS-192

• Order Fields have changed. The "Renewal accordion" on the POL has been replaced by "Ongoing order information" accordion. As a result libraries may want to revisit order templates. existing orders should not be affected as the data will be migrated in the backend.

...

• mod-data-export is a new module which can be used to export bibliographic data in MARC binary format. For Q1 the only supported storage for file export will AWS S3. For configuration steps please see (https://github.com/folio-org/mod-data-export/blob/master/README.md)(For questions contact Kruthi Vuppala / Magda Zacharska )
  (Note: There will be  platform agnostic implementations in future releases)
• raml module builder (RMB) based back-end modules should use RMB version 29.3.* or 29.4.*. The platform core team will provide hot-fixes only for these versions during the period of time where Fameflower is the latest FOLIO release. The module spreadsheet indicates each module's RMB version.
• raml module builder (RMB) based back-end modules should not be installed or updated in parallel but one by one in sequence. Otherwise some might fail with "tuple concurrently updated" (RMB-598).

Known Issues 

• Patron groups that contain non-alpha numeric characters cannot be used for filtering in Users app

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIU-1568

• When you pay or waive a fee/fine from the Fee/Fine Details page, the action will not take effect until you manually refresh the browser page.  If you fail to do so, and enter the payment/waive again, the transaction will be entered again with no way to get rid of it. 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIU-1644

...

• When creating an order line and saving it with the Package toggle disable and then editing it and enabling the package toggle or vice versa could result in unwanted receiving records (receiving titles). This will be handled by the following issue during Q2 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODORDERS-374

• Related invoices are not displayed at the PO level. When processing invoices against POLs you will be able to view the POL and see related invoices. However, even though they display on the POL they will not show as related invoices on the PO. 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVOICE-148

   will complete this work
• Order prefixes and suffixes are not added to the order number during order creation when using the respective dropdown fields on order form. However, you can allow order number to be edited in settings and manually add prefix and suffix to order number in UI. The following issues will resolve this in Q2 and migrate data as needed. 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in (MODORDSTOR-133, MODORDERS-281, UIOR-495, MODCONF-36) serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

• There are two remaining permissions for mod orders that are no longer usable as they have been removed. However, they may still appear in old databases: 'Orders: Check-in items' and 'Orders: Receive/Check-in items'. These permissions will be cleaned up with a script or some additional code in mod-perms for dealing with deprecated permissions. See the following issues for status

  • Jira Legacy
    server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODPERMS-78

    Jira Legacy
    server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODORDERS-382

...

• In some circumstances when creating a new budget you are not able to allocate more than 0 dollars. After creating the budget allocations can be made as needed but the system sometimes chokes when trying to create the allocation along with the budget. 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODFIN-129

• View transactions. If you have viewed a previous budgets transactions you need to click view transactions, click 'x' to close it, click view transactions again to refresh the list. 

  Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIF-210

...

• Matches: Can match between MARC Bibs and Inventory Instances/Holdings/Items only. Will add matching between MARC Bibs and MARC Bibs in Q2
• Actions: Can create MARC Bibs, Inventory Instances, Inventory Holdings, and Inventory Items only. Will add updating for those record types in Q2.
• Field mappings: Can create field mappings for Inventory Instances/Holdings/Items except for 4 specialized types of fields, which will be added as hotfixes for Fameflower:
  • Checkboxes
  • Date pickers
  • Reference values/Dropdowns
  • Repeatable fields
  • Will add field mapping modifications for MARC Bibs in Q2
• Job profiles: Can create job profiles that include the acceptable matches, actions, and field mappings described above. One bug, UIDATIMP-413 needs to be resolved and hotfixed to Fameflower before the job profiles will work properly.

...

New Features by Epic (Sub-Project)

Closed Bugs

All Closed Bugs and Stories

Remaining Open Bugs at Time of Release 

...