From latest to oldest.

This release centers on a substantial OpenAPI Document upgrade — RFC 9457 error responses, request bodies on DELETE operations, an OpenAPI 3.0/3.1 minor-version selector, and the ability to edit a BIE's OpenAPI options directly from its root — together with a broad Business Term overhaul that adds a drag-and-drop import dialog, in-place term management in the BIE editor, and a large set of correctness and integrity fixes. It also introduces developer-controlled sibling sort order for model browsing, a safety warning in the BIE editor, and richer database schema documentation. On the platform side, the score-web front end moves to Angular 21.

• Issue #1347 - OpenAPI Doc: Add error HTTP response codes, using RFC 9457 ProblemDetails schema in an OpenAPI context

• Issue #1610 - DELETE verb expression has no request body or responses

• Issue #1760 - OpenAPI Document: show minor version (3.0/3.1) in the UI and emit the canonical patch on generate

• Issue #1519 - Update BIE root view to include OpenAPI options

  Note on OpenAPI version and DELETE bodies (#1610 / #1760): The OpenAPI Version selector now offers just the minor version (3.0 or 3.1); new documents default to the 3.1 family, and generated documents automatically declare the latest patch of the selected family (3.0.4 or 3.1.2). A DELETE Request message body is expressed only for 3.1 documents — if a document targets 3.0 the body is intentionally dropped, and the editor shows an amber banner to warn you before generation.

• Issue #1754 - Business Term UX: import dialog and in-place management in the BIE editor
• Issue #1753 - Business Term: UX improvements and assignment-list scoping

• Issue #1638 - Add support for sibling sort order for model browsing and BIE editing

• Issue #1755 - BIE editor: warn before an 'Used' un-check clears descendants

  Note on sibling sort order (#1638): Reordering is a developer capability available in the Model Browser (the BIE editor reflects the order but is view-only), attributes remain grouped above elements, and the ordering is release-specific. Custom order carries forward automatically into newly drafted releases; exporting it in the migration script is opt-in via an "Include sibling view order" option.

• Issue #1759 - Augment database schema tables and comments

  This is a documentation-only change — table-level descriptions were added for 60 previously-undocumented tables and column comments were corrected or filled in. There are no structural, column, index, or constraint changes.

• Issue #1757 - OpenAPI Doc: false "Operation ID must be unique" error when saving a request/response operation pair

• Issue #1752 - Business Term: correctness, authorization, and integrity defects

  A broad set of Business Term catalog and assignment defects were fixed, including assignment Discard removing the wrong record, missing server-side authorization on endpoints, a non-working in-use deletion guard, unpersisted list filters, duplicate assignments, and External Reference URI truncation, along with numerous validation and UI fixes.

• score-web front end upgraded from Angular 20.3.25 to Angular 21.2.17 (Issue #1748), including TypeScript 5.9 and the Angular Material/CDK 21 toolchain
• Security and library updates, including jackson-bom 2.21.1 → 2.21.4 (patching jackson-databind CVEs) and jOOQ 3.20.12 → 3.20.17
• Spring Boot remains at 3.5.15

Before proceeding with the upgrade, we strongly recommend backing up your data. As with versions 3.5.0 and 3.5.1, database version management is handled by Flyway. On first startup the backend automatically applies the V3_5_2 migration — which adds the sibling sort-order table, the OpenAPI error-response columns, and the schema table/column comments — so you do not need to manually apply a database migration SQL script during the upgrade.

If you are running connectCenter in a Docker environment, update the following image tags:

• srt-web to 3.5.2
• srt-http-gateway to 3.5.2
• srt-repo to 3.5.2
• redis to 7.4.8

See docker-compose.yml for an example.

This release focuses on OpenAPI Doc improvements, including the ability to define endpoints that do not reference a BIE, a simplified operationId format, and additional security scheme options. It also enhances the BIE Package manifest with backward-compatibility and revision reason information (delivered as a Draft 0.3 manifest — see the note below), introduces GitHub issue tracking for component changes, and resolves several bug fixes. Key platform dependencies are updated as well, including Spring Boot 3.5.15 and Angular 20.3.25.

• Issue #1730 - OpenAPI Doc: Provide ability to define endpoints that do NOT reference a BIE
• Issue #1732 - OpenAPI Doc: Modify the generation of the OperationId to exclude the business context in the name
• Issue #1729 - OpenAPI Doc: Enable the API Key and JWT bearer options as additional security scheme object
• Issue #1731 - OpenAPI Doc: move the Discard button away from the Update Button

• Issue #1733 - Populate Backward Compatibility Indicator and Revision Reason Text in BIE Package Manifest

  Partially delivered — emitted only under the new Draft 0.3 manifest (selectable via the Manifest Version dropdown next to Generate; 0.2 stays the stable default). The package-level Revision Reason is complete, but 0.3 is marked Draft because the Backward Compatibility Indicator design is not yet final: the confusing syntaxIndependent indicator will likely be dropped in favor of the XML/JSON indicators, the JSON scalar→array cardinality-flip break is still unresolved, and the rule set needs further review. See the issue's comments.

• Issue #1533 - Score to track github issues for component changes

• Issue #1728 - OpenAPI Doc: Two separate schema objects are created for the same BIE

• Issue #1744 - Cannot update an existing Context Scheme — uniqueness check treats the scheme as a duplicate of itself
• Issue #1738 - Remove duplicate 'Move to WIP' toolbar button from CC/DT/BIE list pages
• Issue #1737 - createAscc rejects the first ASCC against a non-reusable ASCCP
• Issue #1735 - Unexpected Results When Uplifting a BIE with Reuse BIEs
• Issue #1723 - Codelist value domain value not showing in UI

• Spring Boot upgraded to 3.5.15
• Angular upgraded to 20.3.25
• Routine library and security updates, including jOOQ, Netty, Lombok, MariaDB Java client, Log4j, springdoc, Spring AI, AspectJ, PlantUML, json-schema-validator, and XSOM

Before proceeding with the upgrade, we strongly recommend backing up your data. As with version 3.5.0, database version management in 3.5.1 is handled by Flyway. As a result, users do not need to manually apply a database migration SQL script during upgrade.

If you are running connectCenter in a Docker environment, update the following image tags:

• srt-web to 3.5.1
• srt-http-gateway to 3.5.1
• srt-repo to 3.5.1
• redis to 7.4.8

See docker-compose.yml for an example.

This release includes significant enhancements to BIE expression and packaging, expanded JSON Schema and OpenAPI support, and several fixes for OpenAPI document generation and BIE behavior. It also updates key platform dependencies, including Spring Boot 3.5.13, Angular 20.3.18, MariaDB 11.8.6, and Redis 7.4.8.

• Issue #1703 - Add Expression Format Options to Generate BIE Package
• Issue #1711 - Ability to Express BIEs with File Names Having a Preferred Pattern
• Issue #1712 - BIE Expression Option with Separated Reuse BIE and Reuse BIE Types In Separate Files
• Issue #1713 - Reusable BIE Type Expression - JSON Schema
• Issue #1714 - Reusable BIE Type Expression - XML Schema
• Issue #1311 - Add capability to for stand-alone export in JSON schema format
• Issue #1701 - Json Schema Expression of BIE lacks Descriptions
• Issue #1691 - Pagination Response and Meta Header no longer expressing with BIE

• Issue #1704 - OAS Doc HTTP 500
• Issue #1709 - OpenAPI Doc - Orphaned reference to a Reused BIE that was in a BIE is still being expressed
• Issue #1710 - OpenAPI Doc: Minor Enhancement to generate all path parameters when specified in the Resource name
• Issue #1715 - OpenAPI Doc: Minor Enhancement to add {version} to the resource name and pass in the Document Version into {version} during generation

• Issue #1700 - Enable a modified Core Component Menu item and modified Core Component screen for end user accounts for the all instances including multi-tenant cloud
• Issue #1699 - Allow for BCCP visibility during Browser View for Dev/Admin accounts

• Issue #1708 - Moving Reuse BIE to Production state causes BIEs to also automatically move to Production

• Issue #1628 - Can't cancel recent changes made to a BDT

• Spring Boot upgraded to 3.5.13
• Angular upgraded to 20.3.18
• MariaDB upgraded to 11.8.6
• Redis upgraded to 7.4.8

Before proceeding with the upgrade, we strongly recommend backing up your data. Starting with version 3.5.0, database version management is handled by Flyway. As a result, users no longer need to manually apply a database migration SQL script during upgrade.

If you are running connectCenter in a Docker environment, update the following image tags:

• srt-web to 3.5.0
• srt-http-gateway to 3.5.0
• srt-repo to 3.5.0
• redis to 7.4.8

See docker-compose.yml for an example.

This release includes several enhancements and bug fixes. Detailed information about each change is available in the linked issues below.

• Issue #1659 - Add support for attaching/referencing data definition documentation files (or URI pointing to documentation) to a BIE
• Issue #1678 - Version Change Tracking and Impact Indicators for the BIE Package

• Issue #1704 - OAS Doc HTTP 500
• Issue #1705 - JSON Schema: incorrect required property inside definition object

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.4.2 (example: link).

connectCenter 3.4.1 user MUST upgrade DB schemas through the migration script mig_3.4.1_to_3.4.2.sql before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

This release includes several enhancements and bug fixes. Detailed information about each change is available in the linked issues below.

• Issue #1668 - UI Enhancement: Default library option possibly being connectSpec.
• Issue #1672 - UI Enhancement: Add a Where Used menu option to the browser view of a CC
• Issue #1673 - UI Enhancement: PlantUML option for the Show Diagram option in view bie area
• Issue #1677 - BIE Package Name
• Issue #1683 - Change sign in page label above the credentials form.
• Issue #1684 - Change page titles

• Issue #1670 - Generating OpenAPI expression does not include Context Definition in yml whereas Expressing BIE as OpenAPI does
• Issue #1679 - XSD expression's element declaration contains two Annotation child elements
• Issue #1686 - Add Control-S on BIE edit screen, even when text boxes have focus
• Issue #1687 - Login ID updates

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.4.1 (example: link).

connectCenter 3.4.0 user MUST upgrade DB schemas through the migration script mig_3.4.0_to_3.4.1.sql before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

We are releasing version 3.4.0.1 as a patch update that includes hotfixes addressing several bugs, such as those listed below:

• The log creation time not being displayed correctly.
• The owner name not being displayed correctly in a module assignment page.
• Issue #1665 - Right clicking on a BIE in the view BIE menu no longer shows the default browser menu
• Issue #1667 - Copy BIE with existing Business Context is only rendering the first BIE

If you have already upgraded to version 3.4.0, we strongly recommend updating to this version. Otherwise, please review the 3.4.0 Release Notes and perform the database migration before upgrading to this version.

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.4.0.1 (example: link).

[Deprecated. See 3.4.0.1] This release includes two major new features — BIE Inheritance and Multi-Library Support — along with a few bug fixes. Detailed information about each change is available in the individual issues listed below.

• BIE Inheritance
• Multi-Library Support

• #1643 - Need to increase the size of den columns
• #1655 - Do not copy SVG Logo, favicon, and color theme values during updates and migrations
• #1661 - Context scheme value search in business context does not work for at least one case.

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.4.0 (example: link).

connectCenter 3.3.x user MUST upgrade DB schemas through the migration script mig_3.3.0_to_3.4.0.sql before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

This release includes improvements related to UI enhancements as well as some bug fixes. Here is the list of related issues.

• #1636 - Add a "copy to clipboard" button on the BIE screen
• #1637 - Add model browser view
• #1639 - Add simplified search option
• #1640 - Add simplified search-results view

• #1642 - Cannot delete multiple selected Context Schemes.

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.3.3 (example: link).

This release includes a patch to fix the following issues:

• #1630 Annotation is appearing twice in expressed xsd bies

Accordingly, the previous version 3.3.1 is deprecated, and we strongly recommend upgrading to 3.3.2 if you are currently using it.

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.3.2 (example: link).

This patch release includes several enhancements and bug fixes as described below.

• #1616 - Linking Existing Accounts option for SSO missing developer accounts in the list
• #1625 - Nice to Have - Business Context is not used to Filter BIEs to Copy - Pre-populate ask
• #1626 - prepopulate definition on new component

• #1622 - Transfer Ownership UI Issue, if you click on a username in the transfer ownership list it shows a not-found works message.
• #1623 - BIE Uplifting Issue: Users unable to uplift BIE's that the user owns, but can uplift other users BIEs
• #1624 - Unable to reuse BIE as a common response body for OpenAPI document

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.3.1 (example: link).

• #1603 - OpenAPI - refine naming convention and check for duplicate topLevelBIE by id
• #1615 - BIE Package
• #1617 - Version Info no longer appearing in BIE expression (.XSD)
• #1618 - Ability to Add/Remove Business Contexts from Production BIEs.
• #1619 - Validate for multi-level extension existence during component creation
• #1620 - Duplication property term check

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.3.0 (example: link).

connectCenter 3.2.x user MUST upgrade DB schemas through the migration script mig_3.2.0_to_3.3.0.sql before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

This patch release includes several enhancements, such as updating the OpenAPI document expression and administrative features. Below is a list of issues in this milestone:

• #1576 - Admin capability to transfer WIP BIEs owned by any users
• #1577 - Ability to disassociate SSO with an account or to merge to account together
• #1597 - BIE's GUID should use a Top-Level ASBIEP's GUID
• #1602 - AVSC schemas are generating with invalid integer field
• #1603 - OpenAPI - refine naming convention and check for duplicate topLevelBIE by id
• #1604 - Reducing the amount of steps need to edit a nested reused bie

• #1587 - BIE Editability Restriction When EUACC is WIP and EUASCCP is Production
• #1588 - OpenAPI Document list not displaying properly in Chromium - previously worked fine.
• #1589 - OpenAPI document - insert into oas_resource_tag when updating BIE
• #1590 - OpenAPI document, suppressing root property no longer working
• #1591 - OpenAPI generated expression: Extra schemas created, two unused, same referenced BIE should not have be duplicated but set as global property
• #1592 - BIE referenced but not expressed in OpenAPI document
• #1601 - No longer can discard an OpenAPI document - Discard's forbidden! The OpenAPI Doc is used.

If you are running connectCenter in a Docker environment, you need to update the srt-web and srt-http-gateway Docker image tags to version 3.2.2 (example: link). Additionally, the srt-repo image has also been updated to version 3.2.2 to patch MariaDB to version 11.0.5. You can optionally choose to use this image.

Furthermore, the external-api module is now available. To integrate it, please refer to this guide for configuring it in your current docker-compose.yaml configuration.

This patch release includes several enhancements, including a variety of changes related to Open API documents (thanks to @dubnemo) and addressing critical security concerns (thanks to @smorgan19). Here is a list of issues in this milestone:

• #1193 - Refactor a property to a based ACC
• #1519 - Update BIE root view to include Open API options
• #1569 - When Deleting a BIE, check to see if the BIE is referenced in an OpenAPI document
• #1570 - Add BIE Release to Edit OpenAPI Document view
• #1571 - OpenAPI Document Generated YML - PATCH request and response are swapped
• #1574 - Refined custom x-oagis-* properties move to the BIE level, add x-oagis-bie-uri
• #1584 - Http Gateway Image is showing 2 critical vulnerabilities associated with CVE-2023-28531 and CVE-2023-45853

• #1579 - Releases Details What's Changed Feature/Button available for End User Accounts

If you are running connectCenter in the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.2.1 (Example: link).

In addition, the external-api module is now available. To use it, please read this guide on setting it up in your current docker-compose.yaml configuration.

This release includes several enhancements, including addition of the 'OpenAPI Document' menu to manage merged OpenAPI expressions, moving den columns from CC history tables to CC manifest tables, etc. Here are some of the key changes:

• #1221 - REST API support for SCORE to access/update its contents (BIE, Schema, CC, OAGIS spec) to support tool integration and automation (Special thanks to @lmkennethburnett)
• #1298 - Enable Deprecation of a property on a BIE for OpenAPI support
• #1492 - Consider an interim approach to generate and merge multiple OpenAPI YML files into one file (Special thanks to @dubnemo and @bingqi2045)
• #1553 - Provide ability to delete multiple notification messages
• #1558 - Update connectCenter colors to better reflect our brand color template
• #1562 - Move den field from CC tables to CC_manifest tables

If you are running connectCenter on the docker environment, you need to update the srt-web, srt-http-gateway, and srt-repo docker image tags to 3.2.0 (Example: link).

Score 3.1.x user MUST upgrade DB schemas through the migration script mig_3.1.0_to_3.2.0.sql before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

This is a patch release to fix a module set release validation failure for connectSpec 10.10.1. If you are running connectCenter on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.1.2 (Example: link).

• #1551 - Validation 500 error when running module set release validation

This release contains several bug fixes and small enhancements. Here is a list of changes:

• #1524 - New User Banner or Help Area on the Login Page
• #1529 - Add 'Find Reuses' menu option in View/Edit BIE popup menu
• #1535 - Update Score logo to connectCenter logo for tenant.oagiscore.net
• #1537 - Update the Score favicon to the new connect favicon

• #1506 - Change the structure of the BCCP DEN with the DT DEN
• #1543 - AVSC schema generates an invalid schema when a component has no children attributes
• #1546 - Error when updating BIE with new code lists
• #1551 - Validation 500 error when running module set release validation
• #1552 - Revised core components in WIP state will produce a bug in creating release draft process

Please see Score 3.1.1 milestone for more details.

If you are running Score on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.1.1 (Example: link).

Please see the upgrade instruction

This release includes several enhancements and bug fixes, including 'Convert Database to MariaDB', addition of AVSC/AVRO as an Expressable schema format, etc. Here are some of the key changes:

• #1526 - Convert Database to MariaDB
• #1500 - Addition of AVSC/AVRO as an Expressable Schema Format
• #1520 - View BIE - Search BIEs across any Branch

• #1538 - Error expressing JSON Schema in demo.oagiscore.ent
• #1536 - Cannot change the BDT of Value BCCP

This is a patch release included changing a logo, updating BCCP DENs, and bug fixes. If you are running Score on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.0.4 (Example: link).

• #1505 - Logo changed
• #1506 - Change the structure of the BCCP DEN with the DT DEN

• #1483 - OpenAPI Expression - When expressing an array, make the inner object a global property, and have the array reference that property
• #1383 - missing format check for the external csv file upload
• #1501 - Definition should not be overwritten in the derived BDT if it was changed earlier
• #1504 - Revision number is reset to 1 after the SC is removed

This is a patch release included several enhancements and bug fixes. If you are running Score on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.0.3 (Example: link).

• #1481 - OpenAPI Expression - Enable reusable global schema when a BIE references a reusable BIE
• #1482 - Feature Request: Retain Enabled Properties, including their primitives, cardinality, and context definitions of a reused BIE when user disables its reuse
• #1483 - OpenAPI Expression - When expressing an array, make the inner object a global property, and have the array reference that property
• #1484 - Use of Pattern keyword for date related primitives.
• #1491 - Use a different background color for each role.
• #1494 - Add a "Components" tab to the home screen dashboard for displaying Component related work
• #1495 - Add control-S/command-S hotkey functionality for saving when on the BIE edit screen and component edit screen

• #1486 - Removing a Reused BIE at Lower Level removes a higher level reference to a different reused
• #1488 - Cannot update the description of a Context Schema Value

This is a patch release included several enhancements and bug fixes. If you are running Score on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.0.2 (Example: link).

• Note: the srt-repo image has been updated to 3.0.2 to keep up with the base image, MySQL, which has been updated from 5.7.41 to 5.7.42. Please consider updating the version of the srt-repo.

• #1469 - Allow BCCs referencing BCCPs based on Open Identifier to be selected as an integer (override feature)
• #1472 - Change the prefix "oagis-id-" with "_" for the "id" attribute in XML schema
• #1473 - Allow mass status update of BIEs from WIP -> QA -> Production similar to Core Components

• #1470 - Generated migration script does not contain *_manifest_tag records.
• #1471 - "413 Request Entity Too Large" Response during BIE updating.
• #1476 - Confirm Verb tagged as Noun

This is a patch release included several enhancements and bug fixes. If you are running Score on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 3.0.1.

• #1424 - Set Base ACC - make Conflicts a dialog box that forces me to either click OK or Copy to Clipboard
• #1447 - Add validation function for the module set release
• #1452 - Add 'Generate Migration Script' function
• 'Stand-alone' export in XML schema format - Related to #1311 - Add capability to for stand-alone export in JSON schema format

• #1356 - Uplifting BIE feature is not uplifting attached Code lists
• #1458 - Create Business Term: cannot paste the full length of a URI
• #1460 - XML schema generated via Module Set Release should use 'import' if the reference has a different namespace
• #1464 - Long Definitions for Business Terms mark through the Updated On Column

This release includes several enhancements and bug fixes, including multi-tenancy, business term management, tagging, etc. Here are some of the key changes:

• #1346 Update database and BIE retrieval to support multi-tenancy
• #602 Create Business Term capabilities map to BIE tables and relate to a data catalog
• #1047 Add a "OAGIS Entity" filter to CC VIew/Edit page and also ASCCP selection page for BIE creation
• Upgrade Angular to 14.2.12 and Spring Boot to 3.0.4
  • #1333 Angular v14
  • #1425 Http-Gateway Image Contains 2 Critical Security Vulnerabilities

• #1353 Fail to update context scheme value that derived from the code list
• #1365 'My recent BIEs' and 'My unused extensions in BIEs' panels in homepage doesn't show DEN
• #1393 If the code list is in Deleted state it should be displayed using Strikethrough font for the code list selection
• #1431 "Update" button unexpectedly disabled when editing BIE
• #1445 Nothing's happened during creating a new module set with 'default' option.

Please see Score 3.0 milestone for more details.

Score 2.4.x user MUST upgrade DB schemas through the migration script mig_2.4.0_to_3.0.0.sql before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

This is a patch release included several enhancements in OpenAPI expression. If you are running Score on the docker environment, you need to update the srt-web and srt-http-gateway docker image tags to 2.4.1.

• Add option to suppress root property to OpenAPI expression
• OpenAPI template is missing operationId
• Add Security Scheme capabilities to the OpenAPI template

• BIE Expression → Open Document Spreadsheet fails for all types (ODS, FDOS, XLSX)

This version is a patch release to fix the reported bugs. Score 2.4.0 users need to upgrade the srt-web and srt-http-gateway docker image tags from 2.4.0 to 2.4.0.1.

• Uplifting BIE needs warning message under verification when reused BIEs need to be mapped, and other potential issues #1350
• Spring Security Core Critical Vulnerability in Http-Gateway Image #1354

Score 2.4.0 has DB schema changes. Score 2.3 user MUST upgrade DB schemas through the migration script mig_2.3.0_to_2.4.0.zip before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

• Create Open Document Format expression capabilities to handle large volumes of data in Comma Separated Value (CSV) format as well as supporting needs of Small, Medium-sized Enterprises #992
• Create pop up message warning of specific property conflicts when re-assigning Base ACC to another ACC #1024
• Show cardinality in the CC and BIE tree #1045
• Modify OAS expression to use OAS extensions to hold the guid, eliminate guid from reference to have cleaner code generation #1148
• Improve the real estate of the Code List UI #1156
• Add Name and Description fields to Module Set Release (MSR) #1177
• Display the number of files and directories on the Edit Module Set page #1178
• Display the number of assigned CCs to the CC assignment page #1179
• Change BIE pages to show DEN instead of just property term #1188
• Enhance algorithm to check for duplicate property when adding a new one #1192
• Add the ability to get a url link pointing directly to BIE's component/attribute level object #1254
• Change labels 'OAGIS Developer' to 'Standard Developer' #1288
• Express identifier as id in JSON properties #1301
• OpenAPI Expression issue: Eliminate duplicate schema object in OAS yaml when the same BIE is referenced #1302
• Update Resource Path in OAS expression to include Business Context and Version #1308
• Have 'Code Generation Friendly' feature become the default and only behavior and eliminate the non-code-gen option from the UI #1338

• Compare in history showed incorrect content #1185
• Unable to uplift from 10.8 to 10.8.1 in v2.3 on oagiscore.net - infinite loop #1291
• Code List name in BIE Expression doesn't properly show the value of the agency ID list value. #1329
• OAGIS 10.8.3 Module Release cannot be exported with a new agency ID list revision. #1330
• The value domains for CDTs show empty or null value. #1337

Please see 2.4.0 milestone for more details.

This is a patch release to fix a critical bug that admin end-users can't access 'Pending SSO' menu. Users who have not relied on OAuth2 identification providers, such as 'OpenID Connect', have no need to update this version. Another issue is to update docker images to fix critical vulnerabilities recently reported in the CVE. Thanks to @smorgan19 for reporting this issue.

Issues:

• #1293: Srt Repo Image 2.3.0 contains a critical vulnerability
• #1306: Redis image contains a critical vulnerability
• #1307: End User Admin accounts reverts back to the login page when Pending SSO page is selected

Please see 2.3.1 milestone for more details.

This release contains several important changes (DT Management, Agency ID List Management, Module Management), new features (ACC Refactoring, Seperating Admin role), and bug fixes.

Please see 2.3.0 milestone for more details.

Follow the installation instruction here.

Since Score 2.3.0 has DB schema changes, Score 2.2.0 user MUST upgrade DB schemas through the migration script mig_2.2.0_to_2.3.0.zip before application upgrading. It is a normal SQL script, and any preferred MySQL client could be used to execute the script. If you have no MySQL client, MySQL Workbench could be an option.

It reported a Score repo docker image upgrading issue, especially from v2.1. We made a change to make volume ownership to non-root privileges, and it causes a conflict. Here's an error message:

score-db-1 | 2022年06月27日 13:05:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.38-1debian10 started.
score-db-1 | 2022年06月27日 13:05:38+00:00 [Note] [Entrypoint]: Initializing database files
score-db-1 | mysqld: Can't create directory '/var/lib/mysql/' (Errcode: 17 - File exists)
score-db-1 | 2022年06月27日T13:05:38.242209Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
score-db-1 | 2022年06月27日T13:05:38.243438Z 0 [ERROR] Aborting
score-db-1 | score-db-1 exited with code 1

If you have the same problem, first make a backup data. And clean up all docker containers and volumes using docker-compose rm and docker volume prune commands. The following is an example with these commands:

$ docker-compose rm
? Going to remove score-frontend-1, score-backend-1, score-db-1, score-redis-1 Yes
[+] Running 4/0
 ⠿ Container score-redis-1 Removed 0.0s
 ⠿ Container score-backend-1 Removed 0.1s
 ⠿ Container score-frontend-1 Removed 0.0s
 ⠿ Container score-db-1 Removed 0.0s
$ docker volume prune
WARNING! This will remove all local volumes not used by at least one container.
Are you sure you want to continue? [y/N] y
Deleted Volumes:
score_db-volume
score_redis-volume
Total reclaimed space: 846.8MB

After that, run docker-compose up -d command and import a backup file to restore data.

This release contains not only new Score features and fixes but also the new OAGIS 10.7.2 release and Score DB schema update.

The main changes to the core component(CC) are as follows.

• Where Used functionality has been added. You can immediately see which CCs a particular node is related to in the tree. See details
• Supplementary components can be excluded from the search with a CC tree as default. It can be turned on/off by a checkbox UI. Similar feature also available on the BIE tree. See details

The main changes on the BIE are as follows.

• You can create a BIE from an End-User CC. See user guide in the Help menu for some restrictions to ensure the consistency between the BIE and CCs as they can still be changed. See details
• The Reset button was added to the BIE detail pane. It returns BIE data to the initialized CC's data. See details
• Deprecated CCs are shown as gray background in the BIE tree. See details

In addition, UI improvement and bug fixes have been added. Please see 2.2.0 milestone for more details.

Follow the installation instruction here.

**It is important **to execute this After installation script right after the docker deployment before any use. This script is needed to distinguish between core components created by users of the standard (in on-prem instances) and core components created by a standard body.

In case you need help, here's the guide for Connect to Score database.

There are two steps to 2.2.0 upgrade since there are database changes. Make sure your current version is 2.1.0, if not perform upgrades in sequence of the Score releases.

1. Upgrade the database. You should take down the application server to prevent any changes to the data during the upgrade.

1.1 Make a backup data before upgrade database.

1.2 If Score v2.1.0 was installed from the green field.

• Please execute this java command line program before executing the database migration script - mig_2.1.0_to_2.2.0.sql.zip. It is needed to distinguish between end-user core components and developer core components.
• Note, it is assumed that there is no core component that has been revised or created with a Developer account. If your instance has undergone such action please contact Score developer team at hakju.oh@nist.gov.

A command line example for localhost is as follows.

 ```$bash
 $ java -jar Score2.2.0-migration-program.jar --host=localhost --user=oagi --password={YOUR PASSWORD}
 -------------------------
 Relocate User data.
 -------------------------
 Relocate user data...
 Update relative data...
 Completed.
 ```

1.3 If Score v2.1.0 was upgraded from the previous release

• Only execute the database migration script mig_2.1.0_to_2.2.0.sql.zip.

2. Upgrade the front end components

If you are using a docker-compose.yml file, you can use the instructions as shown below. Note that srt-web image now exposes 4200 port instead of 80 for mitigating security concerns.

• srt-web image got updated to 2.2.0

  - image: oagi1docker/srt-web:2.1.0
  - ports:
  - - 4200:80
  + image: oagi1docker/srt-web:2.2.0
  + ports:
  + - 4200:4200

• srt-http-gateway image got updated to 2.2.0

  - image: oagi1docker/srt-http-gateway:2.1.0
  + image: oagi1docker/srt-http-gateway:2.2.0

  Also, srt-http-gateway container now has allocated 4G memory resources.

  - depends_on:
  - - db
  - - redis
  + depends_on:
  + - db
  + - redis
  + deploy:
  + resources:
  + limits:
  + memory: 4096M
  + reservations:
  + memory: 2048M

Release detail - 2.1.0 milestone

Follow the installation instruction here.

As always, before upgrade with database changes, back up your data first. And you have to upgrade to the previous release before this upgrade, skipping releases is not allowed.

There are three steps to this upgrade that has to be done in this specified sequence. 1) Update data which includes fixing some data and syncing OAGIS data including 10.7.1 and working branch. 2) Update database schema. 3) Update and redeploy Score 2.1.0 docker-compose.yml file.

Please download

For java 11: Score2.1.0-migration-program.jar

For java 8: Score2.1.0-migration-program.jar

And execute it in an environment where Score database is accessible. We will use this program to accomplish two tasks **a) fix BIE data and **b) adding OAGIS 10.7.1 data. Instruction for each of these task is provide provided after the command line options below.

your console$ java -jar Score2.1.0-migration-program.jar -h
Usage: scoremig [-hV] [--password[=<password>]]... [--host=<host>]
 [--port=<port>] --type=<type> --user=<user>
Score migration program.
 -h, --help Show this help message and exit.
 --host=<host> Host on which Score Repository is located. Default:
 localhost
 --password[=<password>]
 Password to use when connecting to server.
 --port=<port> TCP/IP port number for connection. Default: 3306
 --type=<type> Task name to be executed. Available: 'oagis1071',
 'fixprimitive'.
 --user=<user> Score Repository user name to use when connecting to
 server.
 -V, --version Print version information and exit.

The first task is data correction. During BIE's Uplift process, we found that the BIE of 10.7 is referring to the code list of 10.6. This task finds incorrect references of 10.7.0.1 BIE and replaces them with a valid code list.

Please use --type=fixprimitive to execute this task. An example command line for localhost is as follows.

your console$ java -jar Score2.1.0-migration-program.jar --type=fixprimitive --host=localhost --port=3306 --user=oagi --password
Enter value for --password (Password to use when connecting to server.):

If the program found that there are data that need to be fixed, you will get the message like below. If not, the program exits and the task is finished (i.e., no data need to be corrected).

---------------------------------------------------------
Fix primitive info of 10.7.0.1 BIE uplifted from 10.6 BIE
Note: If your Score instance has only OAGIS 10.7 please upgrade it to 10.7.0.1 First.
---------------------------------------------------------
Database connected.
Step(1/2) Search for 10.6 end-user code lists that are used by 10.7.0.1 BIEs.
NAME	|	GUID	|	LIST ID	|	VERSION	|	AGENCY ID	|	OWNER
CL_10.6_only	| dfe64a982c294cdaa17a5fda5b96273b	| 606caa5210c34b8d84efcfcb383b9a12	| 1	|	402	|	khlee
CL_10.6_and_10.7.0.1	| bd595c4d31a24c59a20609b6527c3e0e	| c6a9aad078da456bbdf80864e6a33c57	| 1	|	402	|	khlee
CL_duplicated_name_case	| 2b52f057adad44ac9fe3c4fc516ab5dd	| c14b81b45dd24d0fbce14eb32a117eb3	| 1	|	402	|	khlee
3 code list(s) from 10.6 above have been found that are used in 10.7.0.1 BIEs.
Please uplift these code lists to 10.7.0.1 before continuing otherwise they will be replaced with default primitives.
Press Enter to continue.

Through this step, check the required code list in 10.7.0.1 and uplift the required code list through the Score. Once done with code lists uplift, press Enter to proceed to the next step. It is important to note that if there is no corresponding code list in 10.7.0.1, the troubling BIE nodes will be updated to point to its default primitive instead. After hitting Enter, the program proceeds to step 2 and you will see messages similar to the code block below based on the following three situations. For the the third situation, a user input is needed:

1. Can not find same name code list.
   • The node will be updated to its default primitive.
2. Only one code list found.
   • The node will be updated to referring to found code list.
3. Multiple code lists found.
   • The matching list is displayed, selectable among them.

Step(2/2) Fix the BIEs that use these 10.6 code lists to use the 10.7.0.1 code list.
---------------------------------------------------------
Attention! - The top-level BIE with `Get Item Master[248b94f07f884688ae77ae32a0c62935]` has the node `Get Item Master/Data Area/Item Master/Identifier` updated to its the default primitive from `CL_10.6_only` because there is no code list with the same name.
---------------------------------------------------------
Top Level BIE `Get Item Master[248b94f07f884688ae77ae32a0c62935]` has the node `Get Item Master/Application Area/Receiver/Sequence Number` that uses a 10.6 code list.
There is a code list in 10.7.0.1 with the same name shown below. It will be used to replace the 10.6 code list ::
NAME | GUID | LIST ID | VERSION | AGENCY ID | OWNER
CL_10.6_and_10.7.0.1 | 370445aa79404bb68ea1e7cf08684be6 | 755f463bf4684324b1d1e3e446eaa162 | 1 | 402 | khlee
---------------------------------------------------------
Top Level BIE `Get Item Master[248b94f07f884688ae77ae32a0c62935]` has the node `Get Item Master/Application Area/Correlation Identifier` that uses a 10.6 code list. There are 2 code lists in 10.7 with the same name shown below. Please select one to replace.
INDEX | NAME | GUID | LIST ID | VERSION | AGENCY ID | OWNER
1. | CL_duplicated_name_case | 99565d68916344bf911375263f6e7ad0 | c58197f2ac844798add484ead608f83e | 1 | 402 | khlee
2. | CL_duplicated_name_case | 7b3e2c46d8964ed1a28eef3e039ae4ed | 345526b3091c468b92c62a94066312dd | 1 | 402 | khlee
Enter the index to select [1-2]:
1
Migration finished.

Please use --type=oagis1071 in the command line to accomplish this task. A command line example for localhost is as follows.

your console$ java -jar Score2.1.0-migration-program.jar --type=oagis1071 --host=localhost --port=3306 --user=oagi --password
Enter value for --password (Password to use when connecting to server.):

This test updates the user's database with the changed data from 10.7.1 and the latest information currently working on it. After the data migration is done, update the schema for Score 2.1.0.

-------------------------
Add OAGIS 10.7.1 release.
-------------------------
Relocate user data...
Clean up old data...
Insert 10.7.1 data...
Update relative data...
Alter Score 2.1.0 schema...
Completed.

• srt-web image got updated to 2.1.0

  - image: oagi1docker/srt-web:2.0.0.3
  + image: oagi1docker/srt-web:2.1.0

• srt-http-gateway image got updated to 2.1.0

  - image: oagi1docker/srt-http-gateway:2.0.0.3
  + image: oagi1docker/srt-http-gateway:2.1.0

This release fixes bug in the OAGIS 10.7. See 2.0.0.4d milestone for details. Sales Lead Header Base ACC has two associations to the Party ASCCP - one in the CRM Header Base ACC and one in the Sales Lead Header Base ACC itself. To fix OAGIS 10.7, the Party ASCCP in the Sales Lead Header Base has to be removed from the database. This changes results in OAGIS release 10.7.0.1 that replaces OAGIS 10.7 in the Score database.

Follow the installation instruction here.

For upgrade, follow the following update instruction. If there is any BIE depends on the Sales Lead Header Base. Party, it too has to be manually removed. This condition can exist only in the any BIE tree containing a Sales Lead Header node. If the user open a Sales Lead Header node, he will see two Party children nodes, either one or both could be marked as used and has some user data. To prevent lost of data, the update script checks for whether there is any second Party node that is marked as used. If so, the script directs the user to manually migrate/merge data from the second Party node to the first Party node manually. Then, the user has to execute the script again to finish the migration which will delete the second Party node and corresponding CC.

The update script is a java command line program to patch Score data. It can be access at migration-10-7-0-1.jar.zip

###To execute the update script

shell> java -jar migration-10-7-0-1.jar

Enter the information to access the Score database.

--------------------------------------
Migrate the OAGI 10.7 to OAGI 10.7.0.1
--------------------------------------
Step(1/3) Enter the Score database connection details
Hostname(default: localhost)>localhost
Port(default: 3306)>3306
Username(default: oagi)>oagi
Password> 

The program will now connect to the Score DB and inspect the BIEs referring to the core component that need to be removed. If BIEs exist that use the second Party in the Sales Lead Header BIE node, they have to be manually fixed to un-use that second Party node and merge the data to the first node. The script will provide the URL path of the affected BIEs. If the affected BIEs are not in the WIP state, the script will ask the user to confirm updating the state of the affected BIE to WIP.

Find the BIEs that need to be modified and display them with these information URL, name, state.

Step(2/3) Validating BIEs
[domain]/profile_bie/edit/6	Get Sales Lead. Get Sales Lead	Production
[domain]/profile_bie/edit/5	Acknowledge Sales Lead. Acknowledge Sales Lead	WIP
There are 2 BIEs using the second Party node in the "Sales Lead Header". These BIEs must be manually edited to unused the second Party node and move/merge the BIE detail to the first Party node.
Do you want to change the status of all BIEs to "WIP" for editing?(y/n)y
State updated. Please edit the BIEs using Score and then re-run this script again after making correction. 

Case 2-1. If there are BIEs to be modified

If there are BIEs to be modified, the program will change the BIEs to the WIP state. You need to open your Score using the provided URL in browser and change the affected BIEs to do not use the second Party node under a Sales Lead Header node. Then re-run this program.

Case 2-2. If there is no BIE to be modified. The program continue to update the OAGIS data and release number to 10.7.0.1. The script will show the following output.

Step(2/3) Validating BIEs
No BIE is using the second Party node in the "Sales Lead Header".
Press Enter to continue 10.7.0.1 migration.
Step(3/3) Migrate OAGI 10.7 to 10.7.0.1.
10.7.0.1 migration successfully finished.

If there is no BIE to be modified, the program ends after patching the core component data. You can checked in Score that the 10.7 branch has now been replaced with 10.7.0.1. This indicates that the update is completed normally.

If BIEs are returned to WIP because there are 2-1 cases, please make sure to change BIE to the original state after all the work is completed.

This patch release contains several bug-fixes, especially generating invalid BIE expression in case of having multiple reused BIEs and missing 'version' and 'status' properties after copying BIE. See 2.0.0.3 milestone for details. There is no database change so there is no database update or data migration script. Consequently, only oagidocker/srt-web and oagi1docker/srt-http-gateway docker image needs to be updated. The updated image has been uploaded to the Docker Hub. Please update your docker configurations to the new image using the 2.0.0.3 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below.

• srt-web image got updated to 2.0.0.3

  - image: oagi1docker/srt-web:2.0.0.2
  + image: oagi1docker/srt-web:2.0.0.3

• srt-http-gateway image got updated to 2.0.0.3

  - image: oagi1docker/srt-http-gateway:2.0.0.2
  + image: oagi1docker/srt-http-gateway:2.0.0.3

This hotfix release fixes bugs related to CodeList in the BIE editing and BIE expression. For details check closed issues in Milestone 2.0.0.2. There is no database change so there is no database update or data migration script. Consequently, only oagidocker/srt-web and oagi1docker/srt-http-gateway docker image needs to be updated. The updated image has been uploaded to the Docker Hub. Please update your docker configurations to the new image using the 2.0.0.2 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below.

• srt-web image got updated to 2.0.0.2

  - image: oagi1docker/srt-web:2.0.0.1
  + image: oagi1docker/srt-web:2.0.0.2

• srt-http-gateway image got updated to 2.0.0.2

  - image: oagi1docker/srt-http-gateway:2.0.0.1
  + image: oagi1docker/srt-http-gateway:2.0.0.2

This hotfix release fixes bugs related to BIE reuse in the BIE Uplifting and other minor bugs. For details check closed issues in Milestone 2.0.0.1. There is no database change so there is no database update or data migration script. Consequently, only oagidocker/srt-web and oagi1docker/srt-http-gateway docker image needs to be updated. The updated image has been uploaded to the Docker Hub. Please update your docker configurations to the new image using the 2.0.0.1 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below.

• srt-web image got updated to 2.0.0.1

  - image: oagi1docker/srt-web:2.0.0
  + image: oagi1docker/srt-web:2.0.0.1

• srt-http-gateway image got updated to 2.0.0.1

  - image: oagi1docker/srt-http-gateway:2.0.0
  + image: oagi1docker/srt-http-gateway:2.0.0.1

Score 2.0 is a major milestone. The whole core component (CC) management functionality including code list management for end-users, release management, and namespace management, has been added (or revamped) allowing for making a new/revised release of a standard. It is the first time that OAGIS standard, specifically release 10.7, was made on the Score tool. Some parts of CC management functionality are yet to be completed including code list management for developers, agency ID list management, business data type management, module management, and CC serialization.

Score 2.0 also includes a basic BIE uplift functionality that helps the user port BIEs that are based on prior OAGIS releases to a newer release. As part of that the end user code list uplift functionality is also included.

Another significant enhancement includes enhanced performance of BIE and CC trees using Virtual Scroll. While trees may take a little longer to load for the first time, expanding it is much faster even when the node is deep without a lag.

The user will also enjoy the ability to search within both CC and BIE trees to locate the desire property. Simple path based search is also supported with the forward slash.

These are just major enhancements. There are many more including addition of OAS Tag in the API specification expression. For details about all changes, check all closed issues in Milestone 2.0.

Score 2.0 database schema has a very significant change. Therefore, instead of a database upgrade script, a data transfer tool is provided. It is a browser-based tool and has a separate docker image. While the data transfer tool includes a validation step, as an additional layer of assurance a tool to express all BIEs from the Score database is provided. The tool can be used against both 1.7.0.2 and 2.0 instances. Exported BIEs can then be diff/compared to find out if there is any error in the data transfer of the BIE. Both data transfer tool and the BIE expression tool are documented on the data transfer tool wiki page.

To deploy Score 2.0, please use the docker-compose file here.

Released 11/13/2020

This patch release contains one urgent bug fix, Transfer Ownership Bug with SSO Accounts. There is no need to migrate data. Consequently, only oagi1docker/srt-http-gateway docker image needs to be updated. The updated image has been uploaded to the Docker Hub. Please update your docker configurations to the new image using the 1.7.0.2 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below.

• srt-web image got updated to 1.7.0.2

  - image: oagi1docker/srt-web:1.7.0
  + image: oagi1docker/srt-web:1.7.0.2

• srt-http-gateway image got updated to 1.7.0.2

  - image: oagi1docker/srt-http-gateway:1.7.0.1
  + image: oagi1docker/srt-http-gateway:1.7.0.2

Released 10/16/2020

This patch release contains one urgent bug fix of a BIE expression failure in case of nested BIE reuses. This is a patch release with no database change, so there is no need to migrate data. And consequently, only oagi1docker/srt-http-gateway docker image needs to be updated. The updated image has been uploaded to the Docker Hub. Please update your docker configurations to the new image using the 1.7.0.1 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below.

• srt-http-gateway image got updated to 1.7.0.1

  - image: oagi1docker/srt-http-gateway:1.7.0
  + image: oagi1docker/srt-http-gateway:1.7.0.1

Released 10/06/2020

This release focuses on two new features to improve the application usability. Synchronizing Version information with Version Identifier in BOD provides an efficient way to use version metadata in expressed BIEs. Account lock feature also allows to control accounts access control by switching the account status to be enabled or disabled. Furthermore, security audits were performed using OWASP ZAP and the application security has been strengthened, respectively. Please see 1.7 milestone for more details. The users who want to keep the database schema in sync with this release must execute the migration script mig_1.6.0_to_1.7.0.sql. Please see the instruction for the migration process if you are not familiar with this.

As always, before upgrade with database changes, back up your data first.

For the users who upgraded OAGIS 10.5 data to 10.6 by the migration script oagis_10.5_to_10.6.sql in the earlier Score upgrade, patch_oagis_10.5_to_10.6.sql should be executed to fix incorrectly OAGIS 10.5 to 10.6 data migration. This script can be executed at any time during 1.7 Score upgrade.

oagi1docker/srt-web, oagi1docker/srt-http-gateway, and oagi1docker/srt-repo Docker images for this release have also been uploaded to the Docker Hub. Please update your docker configurations to these images using the 1.7.0 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below. Note that if srt-repo container already has a data volume in local, it will not be updated by changing the tag. In this case, apply the database migration scripts above to keep using existing data with the new release; or remove the volume to initialize fresh data for clean installation (note: remove the volume will wipe out all existing data).

• srt-web image got updated to 1.7.0

  - image: oagi1docker/srt-web:1.6.0
  + image: oagi1docker/srt-web:1.7.0

• srt-http-gateway image got updated to 1.7.0

  - image: oagi1docker/srt-http-gateway:1.6.0
  + image: oagi1docker/srt-http-gateway:1.7.0

• srt-repo image got updated to 1.7.0

  - image: oagi1docker/srt-repo:1.6.0
  + image: oagi1docker/srt-repo:1.7.0

After successful deployment of new docker images, the cached data in redis should be deleted with the following command:

1. Access to redis through redis-cli

$ redis-cli -h localhost -p 6379

2. Execute FLUSHALL command

localhost:6379> FLUSHALL
OK

In case of that you don't have redis-cli, you can remove docker volume for redis container by the following command:

$ docker volume ls | grep redis | awk '{print 2ドル;}' | xargs docker volume rm

Released 09/03/2020

In this release, we focus on the integrating SSO issue to support OpenID Connect 1.0 authentication protocol which allows separating an authentication process from Score. Please see the instruction to set up SSO configurations. Also, it has bug fixes including occurring an unexpected error during expressing BIE with Meta Header. Please see 1.6 milestone for more details. The users who want to keep the database schema in sync with this release must execute the migration script mig_1.5.0_to_1.6.0.sql. Please see the instruction for the migration process if you are not familiar with this.

oagi1docker/srt-web, oagi1docker/srt-http-gateway, and oagi1docker/srt-repo Docker images for this release are also updated on the Docker Hub. Please update your docker configurations to these images using the 1.6.0 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below. Note that if srt-repo container has already a data volume in local, it will not be updated by changing the tag. In this case, apply the database migration script to use existing data with the new release; or remove the volume to initialize fresh data for clean installation (note: remove the volume will wipe out all existing data).

• srt-web image got updated to 1.6.0

  - image: oagi1docker/srt-web:1.5.0
  + image: oagi1docker/srt-web:1.6.0

• srt-http-gateway image got updated to 1.6.0

  - image: oagi1docker/srt-http-gateway:1.5.0
  + image: oagi1docker/srt-http-gateway:1.6.0

• srt-repo image got updated to 1.6.0

  - image: oagi1docker/srt-repo:1.5.0
  + image: oagi1docker/srt-repo:1.6.0

Plus, the cached data in redis should be deleted with the following command:

1. Access to redis through redis-cli

$ redis-cli -h localhost -p 6379

2. Execute FLUSHALL command

localhost:6379> FLUSHALL
OK

Released 08/03/2020

In this release, we introduce the BIE reusability by reusing of previously profiled BIEs so that it allows profiling BIEs in a bottom-up fashion. Moreover, the reference of top-level BIEs changes from ABIE to ASBIEP. As a result, users who want to preserve data from the 1.4 release can execute the migration script mig_1.4.0_to_1.5.0.sql instead of initializing database schema from scratch. Please see the instruction for the migration process if you are not familiar with this. You also can look at Score 1.5.0 milestone for more details.

oagi1docker/srt-web, oagi1docker/srt-http-gateway, and oagi1docker/srt-repo Docker images for this release are also updated on the Docker Hub. Please update your docker configurations to these images using the 1.5.0 tag. If you are using a docker-compose.yml file, you can use the instructions as shown below. Note that if srt-repo container has already a data volume in local, it will not be updated by changing the tag. In this case, apply the database migration script to use existing data with the new release; or remove the volume to initialize fresh data for clean installation (note: remove the volume will wipe out all existing data).

• srt-web image got updated to 1.5.0

  - image: oagi1docker/srt-web:1.4.0
  + image: oagi1docker/srt-web:1.5.0

• srt-http-gateway image got updated to 1.5.0

  - image: oagi1docker/srt-http-gateway:1.4.0
  + image: oagi1docker/srt-http-gateway:1.5.0

• srt-repo image got updated to 1.5.0

  - image: oagi1docker/srt-repo:1.4.0
  + image: oagi1docker/srt-repo:1.5.0

Plus, the cached data in redis should be deleted with the following command:

1. Access to redis through redis-cli

$ redis-cli -h localhost -p 6379

2. Execute FLUSHALL command

localhost:6379> FLUSHALL
OK

Released 05/31/2020

This release contains several enhancements such as Updating a landing page with a summary of BIEs and Extensions. The most important enhancement to note is the [Defaulting of the primitives on the BBIEP & Supplementary Component (i.e., fields and attributes) whose data type term is date time, date, and time to the respective primitives] (https://github.com/OAGi/Score/issues/808). Some major bug fixes include Correct default mappings of Date, Time, and DateTime and Unable to show revised extension components up. See Score 1.4.0 milestone for more details.

If you have existing data, the database migration script (mig_1.3.0_to_1.4.0.sql) should be executed to update the database schema and to remove inaccurately generated BIE data (due to #823). Make a backup data before executing the migration script.

oagi1docker/srt-web, oagi1docker/srt-http-gateway, and oagi1docker/srt-repo Docker images for this release also updated on the Docker Hub. Please update your docker configurations to these images using the 1.4.0 tag. If you are using a docker-compose.yml file, you can use the instructions below. Note that if srt-repo container has already a data volume in local, it will not be updated by changing the tag. In this case, apply the database migration script to use existing data with the new release; or remove the volume to initialize fresh data for clean installation (note: remove the volume will wipe out all existing data).

• srt-web image got updated to 1.4.0

  - image: oagi1docker/srt-web:1.3.1.1
  + image: oagi1docker/srt-web:1.4.0

• srt-http-gateway image got updated to 1.4.0

  - image: oagi1docker/srt-http-gateway:1.3.1.1
  + image: oagi1docker/srt-http-gateway:1.4.0

• srt-repo image got updated to 1.4.0

  - image: oagi1docker/srt-repo:1.3.0
  + image: oagi1docker/srt-repo:1.4.0

Released 04/01/2020

This is a patch release that contains bug fixes such as incorrect behavior associated with selection of multiple checkboxes and enhancements for OAS schema generation such as removing GUID from the path in generated OAS schema and relocate a position of examples. See Score 1.3.1.1 milestone for more details.

As we mentioned in 1.3.1 release, this release is needs srt-repo 1.3.0 and you might need to execute the migration script if you have data in the older version of the repo (mig_1.2.0_to_1.3.0.sql).

oagi1docker/srt-web and srt-http-gateway Docker images for this release has also been updated on the Docker Hub. Please update your docker configurations to these images using the 1.3.1.1 tag. If you are using a docker-compose.yml file, you might modify it as follows,

• srt-web image got updated to 1.3.1.1

  - image: oagi1docker/srt-web:1.3.1
  + image: oagi1docker/srt-web:1.3.1.1

• srt-http-gateway image got updated to 1.3.1

  - image: oagi1docker/srt-http-gateway:1.3.1
  + image: oagi1docker/srt-http-gateway:1.3.1.1

Released 03/12/2020

This release has bug fixes including sign-in failure issue by applying a secure-by-default model for Cookies in Chrome 80+ browser and enhancements for searching. See Score 1.3.1 milestone for more details.

As we mentioned in 1.3.0.1 release, this release is needs srt-repo 1.3.0 and you might need to execute the migration script if you have data in the older version of the repo (mig_1.2.0_to_1.3.0.sql).

oagi1docker/srt-web and srt-http-gateway Docker images for this release also updated on the Docker Hub. Please update your docker configurations to these images using the 1.3.1 tag. If you are using a docker-compose.yml file, you can use the instructions as follows,

• srt-web image got updated to 1.3.1

  - image: oagi1docker/srt-web:1.3.0.1
  + image: oagi1docker/srt-web:1.3.1

• srt-http-gateway image got updated to 1.3.1

  - image: oagi1docker/srt-http-gateway:1.3.0.1
  + image: oagi1docker/srt-http-gateway:1.3.1

Released 02/07/2020

This release contains bug fixes that changed primitive types in BIE wouldn't be able to revert (#762) in 1.3.0. If you have not updated to 1.3.0 from 1.2.0 yet, the migration script (mig_1.2.0_to_1.3.0.sql) MUST need to be executed. Note that you need to take a look at 1.3.0 release note before updating. Also see Score 1.3.0.1 milestone for more details.

oagi1docker/srt-web and srt-http-gateway Docker images for this release also updated on the Docker Hub. Please update your docker configurations to these images using the 1.3.0.1 tag. If you are using a docker-compose.yml file, you can use the instructions as follows,

• srt-web image got updated to 1.3.0.1

  - image: oagi1docker/srt-web:1.3.0
  + image: oagi1docker/srt-web:1.3.0.1

• srt-http-gateway image got updated to 1.3.0.1

  - image: oagi1docker/srt-http-gateway:1.3.0
  + image: oagi1docker/srt-http-gateway:1.3.0.1

Released 01/31/2020

This release mainly focused on introducing an expression schema using OpenAPI Specification (#700), improving BIE and Code List functions for usability (#673, #737, #755), and bug fixes. See Score 1.3.0 milestone for more details. The migration script (mig_1.2.0_to_1.3.0.sql) may need to be executed to update the database schema for this release if you want to preserve existing data. Note that make a backup data before executing the migration script.

oagi1docker/srt-repo, oagi1docker/srt-web, and srt-http-gateway Docker images for this release also updated on the Docker Hub. Please update your docker configurations to these images using the 1.3.0 tag. If you are using a docker-compose.yml file, you can use the instructions as follows,

• srt-web image got updated to 1.3.0

  - image: oagi1docker/srt-web:1.2.0
  + image: oagi1docker/srt-web:1.3.0

• srt-http-gateway image got updated to 1.3.0

  - image: oagi1docker/srt-http-gateway:1.2.0
  + image: oagi1docker/srt-http-gateway:1.3.0

In case you are still not familiar with the 1.1.2 and up releases, please see this link for basic installation guide using docker.

Released 10/20/2019

This release contains several enhancements and bug fixes. The user now can create the context scheme by importing code list data (#531) and assign multiple business contexts to BIE (#671). See Score 1.2.0 milestone for more details. By the changes of database schema, the user who has a demand of preserving existing data needs to execute the migration script (mig_1.1.2.3_to_1.2.0.sql). Furthermore, OAGIS 10.6 migration script (oagis_10_5_to_10_6.sql) also is ready. Note that oagis_10_5_to_10_6.sql script MUST be executed before mig_1.1.2.3_to_1.2.0.sql executes. Please make sure to back up data before executing the scripts.

oagi1docker/srt-repo, oagi1docker/srt-web and srt-http-gateway Docker images for this release also updated on the Docker Hub. Please update your docker configurations to these images using the 1.2.0 tag. If you are using a docker-compose.yml file, you can use the instructions as follows,

• srt-web image got updated to 1.2.0

  - image: oagi1docker/srt-web:1.1.2.3
  + image: oagi1docker/srt-web:1.2.0

• srt-http-gateway image got updated to 1.2.0

  - image: oagi1docker/srt-http-gateway:1.1.2.3
  + image: oagi1docker/srt-http-gateway:1.2.0

In case you are still not familiar with the 1.1.2 and up releases, please see this link for basic installation guide using docker.

Released 09/25/2019

This release has focused on a bug fix in regard to the issue #693, that the generated schema may contain duplicate elements. Affected releases by this release are from 1.1.2 to 1.1.2.2. At the same time, users also should execute the migration script to clear duplicate data in DB. See the details of all the issues addressed in this release at the Score 1.1.2.3 milestone page. Make sure to back up your data before executing the script.

oagi1docker/srt-web and srt-http-gateway Docker images for this release also updated on the Docker Hub. Please update your docker configurations to these images using the 1.1.2.3 tag. If you are using a docker-compose.yml file, you can use the instructions as follows,

• srt-web image got updated to 1.1.2.3

  - image: oagi1docker/srt-web:1.1.2
  + image: oagi1docker/srt-web:1.1.2.3

• srt-http-gateway image got updated to 1.1.2.3

  - image: oagi1docker/srt-http-gateway:1.1.2
  + image: oagi1docker/srt-http-gateway:1.1.2.3

In case you are still not familiar with the 1.1.2 and up releases, please see this link for basic installation guide using docker.

Released 07/26/2019 09/05/2019 This release is retired. Users should use/upgrade to 1.1.2.3 directly due to issue #693 involving duplicated data.

In this release, we fixed major bugs in regards to the editing and generating expression BIEs and added 'About' page to recognize which release currently operates on the user system. See the details at the Score 1.1.2.2 milestone page.

Released 05/30/2019 09/05/2019 This release is retired. User should use/upgrade to 1.1.2.3 directly due to issue #693 involving duplicated data.

This release addressed JSON schema generation and other issues logged in Score 1.1.2.1 milestone.

• Released 05/07/2019 09/05/2019 This release is retired. User should use/upgrade to 1.1.2.3 directly due to issue #693 involving duplicated data.

• This is the release that changed from JSF to Angular framework. See Basic Installation Guide using Docker for Score Application Release 1.1.2 and up for Docker deployment instruction. The application logic is intended to be exactly the same as 1.1.1.2d release with no database change. Switching the web application component between the two releases was designed to be possible to reduce the risk of up taking the Angular framework.

• Always make sure that the data is backed up before upgrading.

This release contains upgrading OAGIS 10.4 to 10.5 and new features of the JSON schema generation.

• Issue #590 Upgrade OAGIS 10.4 to 10.5.
• Issue #603 'MetaHeader' and 'PaginationResponse' profiling for JSON schema.

See more at SRT 1.1.1.2d milestone.

This release contains a database change. Please see the Migration Scrip Page, if you are upgrading (not a clean install).

This release contains few bug fixes.

• Issue #575 Missing "items" properties for generating JSON schema as an array.
• Issue #576 Failing to update user-defined core-components' data.

See SRT 1.1.1.1 milestone.

This release contains updating JSON schema generation rules, bug fixes, and user guide documentations for beginners.

• Issue #543, Issue #562, Issue #564 Revise JSON Schema Generation Rules.
• Issue #566 Changes generate schema filename rules.

• Issue #544 Now the main menu at the top-right of the page, the user can access a user guide.

See details about all bugs and enhancements here.

This release contains a schema fix of the srt-repo v1.1.0_0 for MySQL, which contains incorrect unique key on abie table. See the Issue #548.

This release contains a database change. Please see the Migration Scrip Page, if you are upgrading (not a clean install).

This release contains a bug fix related to the code list. Check out the issues fixed in the 1.1.0.2 milestone.

This release contains a bug fix of the JSON Schema Expression which does not reflect changes of BBIE and BBIE_SC primitive types. See the Issue #532.

By this release published, the prior docker image's tag name changes to 1.1.0.0 and the tag 1.1.0 is now pointed to 1.1.0.1 as an alias. This release does not relevant with srt-repo docker images by the SRT release scheme.

This release has a beta JSON schema generation function. It is beta because OAGi JSON/Mobile working group has not finalized the JSON schema Naming and Design Rules and respectively the necessary production rules to generate JSON schema from the SRT repository. Please make sure that your docker-compose.yml file points to the image tags 1.1.0 for both the oagi1docker/srt-repo and oagi1docker/srt-web. Please read below if you are not doing a clean docker-based installation of 1.1.0.

IMPORTANT Please note that there are database changes in this release. For the docker-based deployment, if you have the prior version of the srt-repo docker image, you MUST execute a database script to alter your schema and data (docker will not overwrite existing repository installation even if you have updated the docker-compose.yml file to point to 'oagi1docker/srt-repo`). The script which contains DDL and DML statements can be downloaded here migration script. Optionally, you can read the database change note in 1.0.0 to 1.1.0 document. In order to run the script, you can use any SQL clients like the Oracle SQL Developer. See more details here. Instead, the SQL*Plus in the docker container also can be used. The following command prompt sequences describe how to run the script in the SQL*Plus.

> CNT_ID=`docker container ls | grep srt-repo | awk '{print 1ドル}'` # Suppose that the srt-repo is running.
> docker cp mig_1.0_to_1.1_oracle.sql $CNT_ID:/u01/app/oracle # Copy the script file to the container.
> docker exec -it $CNT_ID /bin/bash # Execute /bin/bash of the container.
root:/# su - oracle # Change the session to the 'oracle' user.
oracle:~$ sqlplus oagi/oagi # Execute SQL\*Plus
SQL> @mig_1.0_to_1.1_oracle.sql # Run the script

The significant change in this release is the UI update. Menus have been changed to consistently use Core Component terminology as the main label while standard specific (such as OAGIS) terms are in the UI component's tool tip and parenthesis of form labels. To display tool tips, the user click on the username drop down menu and select the specific terminology.

It is also IMPORTANT to note that this release has no database change (and hence there is no 1.0.1 tag in the SRT-repo docker repository). However, there is a UI simplification that may affect existing data. Specifically, on the BIE (formerly Profile BOD) page, if you have specified Definition in the text box other than ASBIE Definition and BBIE Definition, the UI in 1.0.1 no longer display those definitions. We assume that no one has used other definitions other than the ASBIE Definition box and the BBIE Definition box.

Other minor fixes and enhancements are also included. Check the "1.0.1 Milestone" in the Issues log.

We have created a link between 1.0.1 tag and 1.0 tag of the srt-web docker images. In this way, the user who pull 1.0 tag will automatically get 1.0.1 tag of the srt-web and going forward the latest 1.0.x releases. This is described in more detail in the OAGIS SRT Environment Installation Guide using Docker

This is the release 1.0 but with MySQL database backend. It is IMPORTANT to note that this is a development test to use MySQL as the backend database. It has not received much testing.

• CC revision was added.
• Release management was added, although still not quite stable.
• User management was added.
• Profile BOD (or now any component can be profiled) can now be managed with multiple OAGIS releases. Although the extension is limited to OAGIS CCs. The end user defined CC (EUDCC) management still need an enhancement.
• Ownership of CCs can be transferred.
• There are also many other bug fixes and UI improvements such as on the Profile BOD editing page - changing the update successful message to a floating dialog box and that the tree position is not reset to the top after the update.

This is the version given to JT. It can handle only one OAGIS release. Limited CC editing, i.e., The user can create/update CC but cannot revise. The profile BOD, Context, and Code List managements are stable. The user can only extend a profile BOD using OAGIS CCs and end user defined CCs.