Title

Introduce Score/connectCenter

Storyboard

https://docs.google.com/presentation/d/1yPWGrJGruvQ3sVPePriq3KC-PQnk5YI4Hncu6Cc4U1I/edit?usp=sharing

Script

[Opening Scene]

Narrator: "Welcome to the introductory video about the Score tool, which is also known as connectCenter. It is an advanced web-based application designed to streamline the development and utilization of data exchange standards."

[Scene transitions to the Score logo with a clean background.]

Narrator: "Score is an open-source name. It has been developed with the collaboration between NIST, OAGi, and its member company. OAGi commercializes Score as connectCenter along with its data exchange standard connectSpec. Score can be deployed empty such that a data exchange standard can be built from the green field, however, leveraging existing standard is recommended. In this video series, the two names, Score and connectCenter, are used interchangeably.”

[Scene transitions to a clean and organized web interface of Score.]

Narrator: "Score addresses the complexities of developing and deploying data exchange standards through traditional file-based formats, such as XML or JSON Schema. By providing a user-friendly, fast, file-format-independent web interface, Score facilitates the entire process for standard developers and end-users with the single source of truth. Score digitalizes the implementation specifications and provides utilities that significantly reduces the complexity of maintaining, analyzing, migrating between different releases of data exchange standards."

[Scene changes to 'CCTS' on the screen with a professional background.]

Narrator: "Based on the UN/CEFACT Core Component Technical Specification, which is also known as ISO 15000-5, or CCTS, Score provides a systematic approach to data standardization and its utilization. We will simply refer to this as CCTS in the rest of the video."

[Scene transitions to a visual representation of the CCTS framework.] => This can be just a table showing the full names and abbreviations of the main entities in two columns.

Narrator: “There are four main entities in CCTS, namely, Core Component or CC, Business Information Entity or BIE, Business Context or BC, and Value list that includes Code List and Agency ID List. Since Agency ID List is hardly changed, we will focus more on the Code List in our video series. Score allow users to manage all of these entities.”

[Scene transitions to relations between these main entities] => This may be a diagram showing relations between the main entities.

Narrator: “CCs represent the standard such as connectSpec. A business context represents the context in which the standard is used. A BIE represents a profile or a subset of a CC in a particular business context. Code list and agency ID list are two ways among others to provide a value domain for a field in a CC and BIE. Sometimes a more restrictive code list is created from another code list for a context specific use in the respective BIE. We will cover details about each of these main entities in other videos.”

[Scene transitions to list main functionalities in Score]

Narrator: “Score provides functionalities to manage CCs, BIEs, BC, Code List, and Agency ID List.
But in addition those, it also provides functionality to express CC and BIE, and to manage Open API document into desired syntactical expression, and lastly to manage Business Term assignment.
In the future, Score will provide a mapping management functionality as well.”

[Scene transitions to show Score User Guide page and show its content and search box]

Narrator: “Finally in this video, I would like to say that if you understand the idea around CCs, BIEs, and Business Context that I explain earlier, Score UI is quite intuitive that you can jump right on. And if you get stuck, it is important to remember that there is a searchable User Guide you can access from the UI. You can jump to the respective BIE or CC management tutorial video respective to you have immediate need or interest. Most standard users start with BIE management.”

[Scene Transition to show BIE creation in the simplest form, i.e., BC is just a name “Third Party Dairy Testing for Milk Pasteurision in Slovenia” using Inspection Order CC]

Narrator: “Although a BIE needs a business context, you can create a business context simply with a short description about your integration goal as a start. I.e., there is no need for other entities inside the business context.”

[Scene Transition: check a few fields in the Inspection Order BIE and add context definitions and save. And then express the BIE as a JSON schema]

Narrator: “Here, I’m going to pick a few fields needed for inspection order and specific definition or developer instructions in my context. Then you can see that there are multiple choices to express this BIE, I’m going to pick the JSON schema. You can see that it is pretty intuitive.”

[Scene Transition to show email member.services@oagi.org and thank you]

Narrator: “You request access to Score or connectCenter demo site today by sending email to member.services@oagi.org. Thank you. Hope you enjoy the video. See you in the next one.”

The End.

[Scene shifts to icons representing each type of Core Component with brief animations.]

Narrator: "Aggregate Core Components, or ACCs, are collections of related pieces of information that together convey a distinct meaning, independent of any business context. In data modeling terms, an ACC represents an entity or object class, contains attributes or properties, and may participate in associations with other ACCs."

[Visual example of an ACC, such as a 'Party Master' entity composed of various attributes and associations.]

Narrator: "Association Core Components, or ASCCs, define the relationships between these entities, enabling the linkage of related data components."

[Visual example of an ASCC showing the association between 'Party Master' and 'Location' entities.]

Narrator: "Basic Core Components, or BCCs, represent the fundamental data elements, such as individual fields or attributes."

[Visual example of a BCC, highlighting a 'System Identifier' field.]

Narrator: "In addition to Core Components, Score utilizes Business Information Entities, or BIEs. BIEs are tailored reflections of Core Components, adapted to meet specific business requirements."

[Scene transitions to a visual of a BIE being customized from a CC.]

Narrator: "For instance, a 'Party Master' BIE would be a customized version of the Core Component, designed to fulfill the unique needs of a particular business context."

[Scene shifts to a diagram showing the relationship between CCs and BIEs.]

Narrator: "Score allows developers to construct standards using Core Components, while end-users can implement these standards through customized Business Information Entities."

[Scene transitions to a section highlighting the 'Code List Management' feature.]

Narrator: "Another essential feature of Score is Code List Management. This functionality enables both developers and end-users to import and utilize predefined code lists, ensuring standardization and accuracy across data exchanges."

[Visual of importing and managing code lists within the Score interface.]

Narrator: "Code lists standardize values such as country codes and currency codes, facilitating seamless integration and interoperability."

[Scene transitions back to the Score logo with a final professional background.]

Narrator: "In conclusion, Score, also known as ConnectCenter, empowers organizations to develop and implement data exchange standards with precision and ease. From Core Components to Business Information Entities and Code List Management, Score simplifies the entire process."

[Closing scene with a call to action.]

Narrator: "Explore how Score can transform your data exchange standards today. Visit our website to learn more and get started."

[Screen fades to the website URL and contact information.]

[End of video]