We are pleased to announce the release of IrisBG version 4.7.1.26031.
This update includes several fixes and improvements across Advanced Search, Authorizations, Custom Attributes, Exchanges and Loans, Reports, and Taxa.
We have focused this release on improving reporting flexibility, strengthening user permissions, and resolving several issues affecting data import and advanced search.
🌱 Download and install the new version from our dedicated Software page.
⚠️ Important: Install the update on all computers using IrisBG. A valid license is required.
💡TIP: Please see our article, Best Practices for Updating IrisBG Across Multiple Users for guidance when updating shared installations.
Table of Contents
Advanced search
Error fix
The advanced search for Item history previously failed when accessed from the Item Management screen. This issue has now been resolved.
Authorization
Improvement: Utilities access control
You can now configure user permissions for the Utilities screens under Authorization>Role types.
This allows administrators to restrict access to system-level utilities such as the Task Scheduler. This is especially helpful for gardens where multiple staff members use IrisBG but only a few administrators should manage system-level tools. This improvement helps prevent unintended configuration changes by users who do not require access to these tools.
Custom attributes
Error fix: Data import with Item custom attributes
Import of new Items with custom attributes failed.
We resolved a bug in the Data Import module that affected imports using custom Item attribute fields (AtrI_ fields).
In some cases, importing new Items that included AtrI_ fields returned the error:
“Unrecognized Accession item.”
This behavior was triggered when custom Item attribute fields were included in the import file. As a result, imports that previously worked without populating ItemNo could fail when AtrI_ fields were present.
This issue has now been fixed, and Item imports that include custom attribute fields will function as expected.
Exchanges and loans
New fields in Exchange packing slips
Two new fields have been added to Exchange and Loan packing slip templates:
• PropHistCode
• PropHistName
These fields allow propagation history information to be included directly in packing slip documentation.
Customizing the packing slip template
Users can customize the XSLT packing slip template used to generate PDF files for exchanges.
The default template file is ExchangeOut.xslt, which creates a PDF containing exchange information. This template can be modified to suit your institution’s needs.
Multiple customized templates are supported. Custom template files must:
- Start with “Exchange”
- Use the .xslt extension
Example:
ExchangeMyCollection.xslt
🌱 Other available fields
The following fields are available for use in customized Exchange and Loan packing slip templates.
| CollectionCode | Collection code |
| EventNo | Exchange number |
| EventDateISO | Exchange event date (ISO format) |
| Quantity | Number of items included in the exchange |
| CollectionName | Institution name, address, institution code, email |
| ContactName | Contact person (name, address, reference person) |
| ContactEmail | Contact email address |
| DeliveryAddress | Shipping address |
| TypeCode | Exchange type code |
| TypeName | Exchange type name |
| Descr | Description |
| Comment | Additional comments |
| SystemName | System name |
| IpenNumber | IPEN number |
| ItemInfo | Locality, collector, collection number, collection date |
| ItemNo | Item number |
| Origin | Origin of material |
| OriginRef | Origin reference |
| PropHistCode | Propagation history code |
| PropHistName | Propagation history name |
| ProvenanceCode | Provence code |
| ProvenanceName | Provenance name |
| ReceivedDateISO | Date received (ISO format) |
| TaxonName | Taxon name |
Reports
Cross-collection search for Insp01
A cross-collection search option has been added to the Insp01: Inspection data report.
This allows inspection data to be queried across multiple collections or properties in a single report.
Important note
To successfully run cross-collection reports, avoid using fields that are specific to individual collections (for example, Location) as search criteria.
Example use case
Some institutions record plant condition inspections as part of ex-situ conservation programs where plants are distributed across multiple properties. Cross-collection reporting allows these inspections to be summarized in a single report for annual conservation reporting.
New search criteria
Two new search criteria fields have been added to the following reports:
Acc02
Item02
Available fields:
- Det. as taxon name
- Received as name
These additions provide greater flexibility when reporting on taxonomic determinations and accession naming history.
Taxa
Improvement: NameLink handling
Handling of NameLink relationships has been improved.
When the accepted taxon name changes, the following name types will now be preserved:
- Cultivars
- Cultivar Groups
- Tradenames
This ensures that horticultural naming information remains correctly linked when taxonomic updates occur
Thank you!
We hope these new features and fixes help support your vital work stewarding plant collections.
🌱 Questions or feedback?
Please reach out to our team — we are always glad to hear from you.
Comments
0 comments
Please sign in to leave a comment.