Component | Latest Version | Updated? | Deployed (Production) | Requires |
|---|---|---|---|---|
|
|
| ||
|
|
| ||
|
|
Announced in #dcb-ops
thread for v8.x
Changes
Related Tickets
dcb-service
v8.7.0
Harvesting, Clustering and Indexing:
Add defensive null code around marc serde field
Search: NA
Request and Circulation workflow: NA
Client Adaptors:
FOLIO: NA
Polaris: NA
Sierra: NA
Logging and error checking:
Log record conversion errors
GraphQL:
Endpoint support for creating singular reference value mappings through DCB Admin (DCB-1619)
Miscellaneous: NA
dcb-admin-ui
v1.28.0
Fix contacts email URL regression [DCB-1756]
dcb-locate
v2.5.0
NA
Deployment
Summary
Environments to deploy to:
Component | GIL Pre-Production | MOBIUS Production | MOBIUS Staging | Integration |
|---|---|---|---|---|
dcb-service |
|
|
|
|
dcb-admin-ui | NA | NA | NA | NA |
dcb-locate | NA | NA | NA | NA |
Change Category | Required | Recommended | Not Required |
|---|---|---|---|
Complete reset |
| ||
Environment configuration |
| ||
Host LMS configuration or setup |
| ||
Service configuration |
| ||
Ingest |
| ||
Index |
| ||
Library configuration |
| ||
Deploy new Executables |
|
Instructions
Deployment will trigger a data migration on service restart.
This can be manually executed before deployment by running the following SQL :
update source_record set processing_state = 'PROCESSING_REQUIRED' where processing_state is null;
When that has completed, dcb-service can then be deployed to the frontend in the same environments.
Verification
After clear down
You can verify that migration has been completed by running
select 'Not finished' where exists (select 1 from source_record where processing_state is null);
This should return 0 rows when complete.