Score User Guide ¶

Revise a BCCP¶

A BCCP in the Published state can be revised where certain changes can be made. Any developer user can revise a published BCCP. He/she does not have to be its owner. To do that:

Find a BCCP in the Working branch.
Open detail page of the BCCP.
Click the “Revise” button at the top-right corner of the page. The BCCP goes into the WIP state and its revision number increases by 1.
The following fields can be updated.
1. Nillable. It can only be updated from false (unchecked) to true (checked).
2. Deprecated. It can only be updated from false (unchecked) to true (checked).
3. Value Constraint. Select “Default” or “Fixed” value constraint in the dropdown list and specify the value in the adjacent field. Note that “Fixed” value constraint and “Nillable” are mutually exclusive, i.e., “Nillable” cannot be true if there is a fixed value constraint and vice versa. Value constraint is optional.
4. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts free form text. Definition Source is optional.
5. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
6. BDT. The associated BDT can be changed.
Click the “Update” button at the top right to save changes.

ASCCP Management¶

Find an ASCCP¶

See Search and Browse CC Library to find the ASCCP needed.

Tip: How to find where an ASCCP is used. ASCC DEN pattern can help locate the ACCs that use a particular ASCCP. Make sure that the ASCC is checked or better yet the only one checked on the Type filter on the Core Component page. In the DEN field input a search string like this “. [ASCCP DEN]”. For example, we can see where “Party” ASCCP whose DEN is “Party. Party” is used by input “. Party. Party” in the DEN field. Note that the double quotes should be included in the search field for more precise match. Note also that ASCC has no detail page, so clicking on the BCC search result does not do anything. To see the detail of the particular ACC, copy the first token of the ASCC DEN, which is the object class term of an ACC and use it as a search input (make sure that ACC is selected in the Type filter).

View detail of an ASCCP¶

Find an ASCCP. Click on the ASCCP DEN after the desired ASCCP is found to open the ASCCP detail page. To understand the detail of the ASCCP, see Quick reference to different types of CCs.

Tip: You can open an “ASCCP detail” page from within another Core Component tree. On any ASCCP node (bolded blue font node), click on the ellipsis next to the node and select “Open in new tab”.

Create a new ASCCP¶

There are two ways to create a new ASCCP.

Create an ASCCP from scratch.
1. If you are not already on, open the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu at the top of the page.
2. Click on the plus sign near the top-right corner of the page.
3. Select “ASCCP”.
4. The ACC selection page is open. Check the check box in front of the desired ACC. The user can use other search filters to find the desired ACC. Certain types of ACCs are excluded from the list including “Extension”, “User Extension Group”, “Embedded”, “OAGIS10 Nouns”, and “OAGIS10 BODs”. For explanation about these different types in Score see Component Types.
5. A new ASCCP is created with revision #1. Its detail page is open with default values populated. The new ASCCP is in the WIP state. The developer may edit the detail of the ASCCP.
Create an ASCCP from an ACC:
1. Open ACC detail page where the current user is the owner of the ACC and the ACC is in the WIP state.
2. Click the ellipsis next to the root node of the ACC tree in the left pane.
3. Select “Create ASCCP from this” menu item.
4. An ASCCP is created with default values. In this case, the property term is defaulted to the same as the ACC’s object class term. The ASCCP is in WIP state. See also Edit detail of an ASCCP.

Edit detail of an ASCCP¶

This section describes ASCCP editing when its revision number is 1.

Open the ASCCP detail page according to View detail of an ASCCP. The ASCCP has to be in the WIP state to be editable. The following fields can be updated.
1. Property Term. Property Term should be space-separated words, each with initial letter capitalized. Acronyms and plural words should be avoided. For OAGIS, it should be what one would expect to see in the expression. For example, a “Customer Party” ASCCP which uses the “Party” ACC should have a property term “Customer Party” (not just “Customer” as CustomerParty is expected in the expression), which would yield “Customer Party. Party” as DEN. In other words, the object class term “Party” is not used in the expression generation.
2. Nillable. Nillable specifies whether a null value can be assigned in the instance data. Nillable is required, but it is defaulted to false.
3. Deprecated. Since this is a brand new ASCCP. The deprecated field is locked.
4. Reusable. This flag supports the notion of local element expression in XML Schema. It is required but it is defaulted to true, which makes the ASCCP analogous to the global element in XML Schema. There are two consequences when an ASCCP is set to not reusable – 1) the application will allow only one ASCC to use the ASCCP; and 2) there can be multiple ASCCPs with the same property term in a single release. In OAGIS, the Data Area component in a BOD is expressed as a local element. In such situation, the ASCCP corresponding to a Data Area would have this flag set to false.
5. Namespace. Select a standard namespace from the dropdown list. See the Namespace Management section to create a standard namespace if needed or how namespace may be used in Score. Namespace is required.
6. Definition Source. Specify the source of the definition. This is typically a URI, but the field is free form text. Definition Source is optional.
7. Definition. Specify the description of the ASCCP. Definition is optional, but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.

Delete a newly created ASCCP¶

See Delete a newly created CC.

Restore a deleted ASCCP¶

Revise an ASCCP¶

An ASCCP in the Published state can be revised where certain changes can be made. Any developer user can revise a published ASCCP. He/she does not have to be its owner. To do that:

Find an ASCCP in the Working branch.
Open detail page of the ASCCP.
Click the “Revise” button at the top-right corner of the page. The ASCCP goes into the WIP state and its revision number increases by 1.
The following fields can be updated.
1. Nillable. It can only be updated from false (unchecked) to true (checked).
2. Deprecated. It can only be updated from false (unchecked) to true (checked).
3. Reusable. It can only be updated from false (unchecked) to true (checked). If the reusable is changed to true, it means that there can be multiple ASCCs using the ASCCP. However, it may cause release invalidation if this results in multiple reusable ASCCP with the same property term.
4. Definition Source. Specify the source of the definition. This is typically a URI, but the field is free form text. Definition Source is optional.
5. Definition. Specify the description of the ASCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.

Cancel an ASCCP revision¶

See Cancel a CC revision.

Change ASCCP states¶

Transfer ownership of an ASCCP¶

See Transfer ownership of a CC

View history of changes to an ASCCP¶

ACC Management¶

Find an ACC¶

See Search and Browse CC Library to find the ACC needed.

Tip: How to find what ASCCPs already exist that are created from a particular ACC. Using the ASCCP DEN pattern along with the double quotes and the Type filter, ASCCPs created from a particular ACC can be better located. For example, type “. Party” in the DEN field and make sure only ASCCP is selected in the Type dropdown will help narrow down the search to ASCCPs that use the Party ACC (the result will also include those that use an ACC whose object class term starts with “Party”).

View detail of an ACC¶

Find an ACC. Click on the ACC DEN after the desired ACC is found to open the “ACC detail” page. To understand the detail of the ACC, see Quick reference to different types of CCs.

Tip: You can open an “ACC detail” page from within another Core Component tree. On any ACC node (bolded red font node or also noticeable with its full DEN ending with “. Details”), click on the ellipsis next to the node and select “Open in new tab”.

Create a new ACC¶

If you are not already on, open the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu at the top of the page.
Click on the plus sign near the top-right corner of the page.
Select “ACC”.
A new ACC is created with revision #1. Its detail page is open with default values populated. See also Edit detail of an ACC.

Edit detail of an ACC¶

This section describes ACC editing when its revision number is 1.

Open the “ACC detail” page according to View detail of an ACC. The ACC has to be in the WIP state, and the current user has to be the owner to be editable. The fields in the details pane may be updated as follows.
1. Object Class Term. Name of the ACC. The value should be space-separated words, each with initial letter capitalized. This field is required.
2. Component Type. Possible values of Component Type are Base, Semantics, or Semantic Group. For explanations about these Component Types, see Component Types. This field is required.
3. Abstract: When the Component Type is set to Base, Abstract is set to true and locked. Semantics Component Type can also be abstract or concrete. Abstract does not apply to the Semantic Group Component Type. This field is required.
4. Deprecated. Since this is a brand new ACC. The deprecated field is locked.
5. Namespace. Select a standard namespace from the dropdown list. See the Namespace Management section to create a standard namespace if needed or how namespace may be used in Score. Namespace is required.
6. Definition Source. Specify the source of the definition. This is typically a URI but the field accepts a free form text. Definition Source is optional.
7. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.
The developer may want to perform these other actions on the ACC:
1. Set another ACC as a base of this ACC.
2. Remove the based ACC.
3. Add a property to the ACC and edit the detail of the resulting BCC or ASCC.
4. Remove a property from an ACC.
5. Order the properties/associations.
6. Ungroup an ASCCP.
7. Change the state of the ACC.
8. Create OAGIS Extension point for an ACC.
9. Create an ASCCP from this ACC.
10. Refactor a property to a based ACC.

View history of changes to an ACC¶

See View Change History of a CC

Set a based ACC¶

On the ACC detail page where the current user owns the ACC and the ACC is in WIP state, click on the ellipsis next to the root node of the ACC tree (on the left pane). Select “Set based ACC”.
A dialog opens up for selecting an ACC. Only Semantics and Base ACC Component Types can be selected, all other types are excluded from the list. Use various filters on the top to find the desired ACC.
Check the checkbox in front of the desired ACC.
Click the “Apply” button.

Tip: OAGIS design pattern typically establishes the base/inheritance relationship between ACC whose Component Type is Base until an extension point is needed. For example, “Personnel Base. Details” is based on “Employee Base. Details”, which in turn is based on “Person Base. Details”. See also Create OAGIS Extension point for an ACC.

Remove the based ACC¶

On the ACC detail page where the current user owns the ACC and the ACC is in WIP state, expand the root node on the ACC tree.
If the ACC has a based ACC, the child node of the root node is the based ACC. Click on the ellipsis next to that node and select “Delete”.
Confirm (or cancel) the based ACC removal.

Add a property to an ACC¶

On the ACC detail page where the current user owns the ACC and the ACC is in WIP state, expand the root node on the ACC tree.
Click on the ellipsis next to the root node and select one of the following menu items – “Insert Property at First”, “Append Property at Last”. Alternatively, click on the ellipsis next to any child property node of the ACC and select “Insert Property Before” or “Insert Property After” menu item. A property node has to be a direct child of the root ACC node. A child property node may be an ASCCP in bolded blue font or may be a BCCP in regular green font.
A dialog is open where the user can select a BCCP or ASCCP. Use filters on the top to find the desired BCCP or ASCCP.
Check the checkbox in front of the desired BCCP or ASCCP.
Click the “Apply” button.
If a BCCP was selected in step 4, a new BCC is created that associates the ACC with the BCCP. The user may edit detail of the new BCC. If an ASCCP was selected, an ASCC is created that associates the ACC with the ASCCP. The user may edit detail of the new ASCC.

Remove a property from an ACC¶

Only a property whose ASCC or BCC is in revision 1 can be removed.

On the ACC detail page where the current user owns the ACC and the ACC is in WIP state, expand the root node on the ACC tree.
Click on the ellipsis next to any child property node of the ACC and select the “Remove” menu item. A property node has to be a direct child of the root ACC node. A child property node may be an ASCCP or a BCCP node. An ASCCP node is noticeable by bolded-blue font, while a BCCP node is in regular-green font.
A dialog is open to confirm or cancel the removal.

Edit details of a new ASCC¶

The section describes the case where the revision number of the ASCC is 1.

On the ACC detail page where the current user owns the ACC, and the ACC is in WIP state, expand the root node on the ACC tree.
Click on a child node of the ACC with the bolded-blue font. The node encapsulates both ASCC and ASCCP information. Detail of the ASCC is displayed in the detail pane on the right side. When the ASCC revision number is 1, its detail can be updated as follows.
1. Cardinality Min. The value shall be a non-negative number that is less than or equal to Cardinality Max. Cardinality Min is required.
2. Cardinality Max. The value shall be a non-negative number that is equal or more than Cardinality Min. The value can also be “unbounded”. Entering -1 to this field is also recognized as “unbounded”. It should be noted that if 0 value is entered, the system will ask for the Definition field to be filled with explanation why it is 0. Cardinality Max is required.
3. Deprecated. This field is locked to false. It cannot be changed because it is a brand new ASCC that shouldn’t be deprecated right away.
4. Definition Source. Specify the source of the definition. This is typically a URI, but the field is free form text. Definition Source is optional.
5. Definition. Specify the description of the ASCC. This is the definition of ASCCP in the context of the ACC. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to accept changes.

Ungroup Properties¶

This function is about changing a content model of some properties of an ACC. This function is available on an association to a group ASCCP (i.e., an ASCCP which uses a Semantic Group type ACC). Ungrouping the association to the ASCCP means refactoring to create associations from the owner ACC directly to properties within the group. To do so,

On the ACC detail page where the current user owns the ACC, and the ACC is in WIP state, expand the root node on the ACC tree.
Locate the association to the group ASCCP in the ACC tree.
Click on the ellipsis next to the ASCC node and select the “Refactor” and then the “Ungroup” menu item.
In the returned dialog, confirm the intention to ungroup the properties.

It should be noted that ungrouping should be done with careful consideration as in certain circumstances it could lead to backward incompatibility change in certain syntaxes.

Edit details of a new BCC¶

The section describes the case where the revision number of the BCC is 1.

On the ACC detail page where the current user owns the ACC, and the ACC is in WIP state, expand the root node on the ACC tree.
Click on a child node of the ACC with the regular-green font or italicized-grey font. The node encapsulates both BCC and BCCP information. Detail of the BCC is displayed in the detail pane on the right side. When the BCC revision number is 1, its detail can be updated as follows.
1. Entity Type. Possible values are Element or Attribute but the field is active only if the BCCP has no Supplementary Component (SC). Otherwise, it is locked to the value Element. The Attribute option is to support the notion of attribute in XML Schema. This field is required.
2. Cardinality Min. The value shall be a non-negative number that is less than or equal to the Cardinality Max. However, the value can only be 0 or 1, if Attribute is selected in the Entity Type. This field is required.
3. Cardinality Max. The value shall be a non-negative number that is equal or more than the Cardinality Min. The value can also be “unbounded”. Entering -1 to this field is also recognized as “unbounded”. However, the value can only be 0 or 1 if Attribute is selected in Entity Type. It should be noted that if 0 value is entered, the system will ask for the Definition field to be filled with explanation why it is 0. This field is required.
4. Deprecated. This field is required, but it is defaulted and locked to false. It cannot be changed because it is a brand-new BCC that shouldn’t be deprecated right away.
5. Value Constraint. This field is activated only when Attribute is selected in the Entity Type. It allows for the Value Constraint in the BCCP to be overridden by the value specified here. Select the Fixed Value or Default Value option and specify the desired value in the adjacent field. This field is optional.
6. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts a free form text. Definition Source is optional.
7. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to accept changes. It should be noted that if Entity Type is Attribute, the node will be moved to the top. On the contrary, if Entity Type is changed to Element, the node will be moved to the bottom.

Order the properties/associations¶

On the ACC detail page where the current user owns the ACC, and the ACC is in WIP state, expand the root node on the ACC tree.
To move a child node of the ACC up or down the tree, click and hold the handle icon (=) of the node and drag it up or down the tree. You may notice that some child nodes at the top of the tree have no handle and cannot be moved. It is because they are BCC whose Entity Type is Attribute.

Delete a newly created ACC¶

An ACC whose revision number is 1 can be (marked) deleted. The ACC has to be in the WIP state and owned by the current user. See Delete a newly created CC.

Restore a deleted ACC¶

Revise an ACC¶

An ACC in the Published state can be revised where certain changes can be made. Any developer user can revise a published ACC. He/she does not have to be its owner. To do that:

Find an ACC in the Working branch.
Open detail page of an ACC in the Published state.
Click the “Revise” button at the top-right corner of the page. The ACC goes into the WIP state and its revision number increases by 1.
Only the following fields in the ACC detail pane on the right may be updated.
1. Deprecated. This can only be updated from false (unchecked) to true (checked). In other words, if the ACC was deprecated in the previous revision, it cannot be un-deprecated.
2. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts a free form text. Definition Source is optional.
3. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.
The developer may want to perform these other actions on the ACC:
1. Set another ACC as a base of this ACC.
2. Remove the based ACC.
3. Add a property to the ACC and edit the detail of the resulting BCC or ASCC.
4. Remove a property from an ACC. Only the ASCC and BCC that are in revision 1 can be removed (added during the current revision can be removed).
5. Order the properties/associations.
6. Refactor a property to a based ACC.
7. Ungroup an ASCCP.
8. Change the state of the ACC.
9. Create OAGIS Extension point for an ACC.
10. Create an ASCCP from this ACC.

Refactor a property in an ACC¶

A property (i.e., ASCCP or BCCP) of a revised ACC in WIP state can be moved (up) to a based ACC or (down) to a derived ACC. To do so,

On the ACC detail page where the current user owns the revised ACC and the ACC is in WIP state, expand the root node on the ACC tree.
Note down the based or derived ACC, to which you want to move the desired property.
Click on the ellipsis next to the property node of the ACC you want to refactor, select the “Refactor” and then the “Refactor to Base” menu item. A page for refactoring the selected property is returned.
1. At the top table of the page select the ACC in which you want to move the selected property.
2. Click the “Analyze” button.
3. At the “Analysis result and required action” section of the page, all the ACC that will be affected by this refactoring are listed. Depending on the case, the following user actions might be needed in order to refactor the property.
  1. An affected ACC is not in WIP state but it is owned by the current user. In this case, click on the DEN of the affected ACC to open it in a new tab and move it to the WIP state.
  2. An affected ACC is in Published state. In this case, click on the DEN of the affected ACC to open it in a new tab and revise it by clicking the “Revise” button at the top-right of the page.
  3. An affected ACC is owned by another user and is not in WIP state. In this case, the user either asks the other user to move it to WIP state or to transfer the ACC ownership.
Once all the required actions are performed, click “Analyze” button again. The message “Ready to refactor” should appear next to all the affected ACCs.
Click “Refactor” button.

The figure below shows an example where the user has refactored Property1 from ACC4 up to ACC1. Both ACC4 and ACC2 are affected as Property1 has to also be removed from ACC2.

The refactored property is inserted at the bottom of the property sequence in the target ACC. In the above example, Property1 is inserted as the last property of ACC1.

Cancel an ACC revision¶

See Cancel a CC revision.

Change ACC states¶

Transfer ownership of an ACC¶

See Transfer ownership of a CC.

View history of changes to an ACC¶

Create OAGIS Extension point for an ACC¶

This is a feature specific to OAGIS design pattern. Each OAGIS component typically has an extension point. The OAGIS extension design pattern is as follows. First, create an ACC whose Component Type is set to Base; its object class term should end with “Base”, e.g., “Party Base”. This is the ACC where all properties reside. Then, create another ACC whose Component Type is set to Semantics and it is based on the first ACC. The object class term of this ACC should be the same as that of the first ACC but without the word “Base”, e.g., “Party”. For OAGIS, the Semantics ACC is where the extension point should be created. Score provides a macro to do that. Necessary entities are created with correct names and properties. To do that.

Make sure the ACC detail page is open, it is in the WIP state, and is owned by the current user. ACC must not already have a property named “Extension”.
Click on the ellipsis next to the root node of the ACC and select “Create OAGi Extension Component”. This menu item is not visible if the ACC already has a property named “Extension”.
A dialog appears asking for confirmation or cancellation.
If confirmed, the ACC will be inserted with the “Extension” property at the bottom. It should be noted that if the user removes the property and invoke this macro again, it will result in duplication extension components created. The user can simply add the existing property extension ASCCP instead of invoking the macro. For OAGIS, the proper extension ASCCP for an ACC is the one with this DEN pattern “Extension. [Object Class Term] Extension”. For example, for “Party. Details” ACC, a proper extension ASCCP is “Extension. Party Extension”. If duplicated extension CCs were created, the user should delete them. The extraneous components would include the extension ASCCP and ACC with DENs such as “Extension. Party Extension” and “Party Extension. Details”. They would have older update timestamps.

DT Management¶

DT Management allows users to create and manage Business Data Types (BDTs).

Find a DT¶

See Search and Browse CC Library to find the DT needed.

Tip: Using the DT DEN pattern that is “Data Type. Type” along with the double quotes can help filter the research result down to mostly data types without having to use the Type filter. For example, type “Amount. Type” (double quotes should be included) in the DEN field.

View detail of a DT¶

To view DT detail:

Find a DT.
Click on the DEN of the DT to open the “DT detail” page.

Create a new DT¶

Only BDT creation is supported. The user cannot create a Core Data Type (CDT). A BDT has to be based on either a CDT or another BDT.

If you are not already on, open the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu at the top of the page.
Click on the plus sign near the top-right corner of the page.
Select “DT”.
1. The “Select based DT” page is open. Click the check box in front of the desired DT to use as the base of the new DT. You can also use the search filters on the “Select bases DT” page to find the desired base DT. For more information about the search filters, see How to use Search Filters.
2. A new DT is created with revision #1. Its detail page is open with default values populated. The new DT is in the WIP state. The developer may edit the detail of the DT.

Score supports both Core Data Type specification v3.1 and ISO 15000-5 Core Component Types as a base of the new BDT. This will result in different sets of supplementary components (SCs) when a CDT is selected as a based DT. At the bottom of the page where a base DT is to be selected, the user has three choices. If the CDT v3.1 is selected (default), the BDT will have SCs per the CDT v3.1. If the ISO 15000-5 is selected, the BDT will have SCs per the ISO 15000-5 Core Component Type definition. If the third choice “None” is selected, the BDT will have SCs from both specifications. Note that the selection of these choices matters only when the base DT is a CDT. If the selected based DT is a BDT, the SCs follow those in the BDT.

Edit detail of a brand new DT¶

This section describes DT editing when its revision number is 1.

Open the “DT detail” page according to View detail of a DT. The DT has to be in the WIP state, and the current user has to be the owner to be editable. The fields in the details pane may be updated as follows.
1. Qualifier: Qualifier field uses tokenize qualifiers. Each qualifier can be added as a string value after the qualifiers inherited from the base DT. A Qualifier can be removed by clicking the x icon. This field is required if the based DT already has a qualifier (however, it does not have to be the same or ends with the existing qualifier). Note: To add a qualifier in front of an existing qualifier, remove the existing qualifier first and type in each desired qualifier token and press Enter in the desired order. Alternatively, remove existing qualifier(s) and type in multiple qualifiers with the under bar and a space separator according to the CCTS specification and press Enter. For example, type in “Total_ Tax” would result in two qualifiers.
2. Six Hexadecimal Identifier. Click the renew icon to generate an identifier for this DT. This field is optional. If specified, this random number will be suffixed to the DT when it is serialized.
3. Namespace. Select a standard namespace from the dropdown list. See the Namespace Management section to create a standard namespace if needed or how namespace may be used in Score. Namespace is required.
4. Definition Source. Specify the source of the definition. This is typically a URI but the field accepts a free form text. Definition Source is optional.
5. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
6. Content Component Definition. Specify the definition of the DT’s Content Component value. This is typically a free form text. Content Component Definition is optional.
Click the “Update” button at the top right to save changes.
The developer may want to perform these other actions on the DT:

Edit Value Domain¶

This section applies to value domain editing of both the DT content component and SCs. Value domains inherited from the based DT or existing in the previous revision of the DT cannot be edited nor discarded.

On the DT detail page where the current user owns the DT, and the DT is in WIP state. Click on the root node of the DT or expand the root node on the DT tree and click on an SC node.
Click “Value Domain” in the detail pane on the right side to expand the “Value Domain” area. The following actions may be performed:
1. Click the “Add” button to add a value domain. Since Score has all possible Primitive value domains for DT content component and SC, only Code List or Agency ID List value domain types can be added. This is allowed only when there is a Token in the primitive value domain type. After clicking the “Add” button, select either Code List or Agency ID List value domain type and then select a specific Code List or agency ID List to use as the value domain. Finally, click the “Update” button on the top.
2. Set the default value domain. Select the default value domain in the dropdown list.
3. Discard a newly added value domain. To do so, click the checkbox in front of the desired value domain and click the “Discard” button. A value domain which is selected as the default value domain cannot be discarded. Change the default to another value domain first, then that default value domain can be discarded.
Click the “Update” button.

Add an SC to a DT¶

On the DT detail page where the current user owns the DT and the DT is in WIP state, expand the root node on the DT tree.
Click on the ellipsis next to the root node and select the menu item – “Add Supplementary Component”. A new SC is added at the end of the DT tree. The default DEN of the SC node is in the format “[Data Type Term of the DT]. Property Term [a number]. [Representation Term]”.
Click the SC on the tree to Edit details of a new SC.

Edit details of a brand new SC in the DT where it was added¶

The section describes the case of editing an SC added to the DT. The SC should have already been added in the latest revision of the DT.

On the DT detail page where the current user owns the DT, and the DT is in WIP state, expand the root node on the DT tree.
Click on an SC node of the DT. The detail of the SC is displayed in the detail pane on the right side of the page.
1. Property Term. Property term should be unique across all SCs derived from this DT as well as within the DT itself. This field is required. It must be space-separated words, each with initial letter capitalized.
2. Representation Term. Click on this field and select the representation term of the SC in the dropdown list. This field is required.
3. Cardinality. The Cardinality field can be Optional or Required. To select the Cardinality of the SC, click the Cardinality field and select either Optional or Required.
4. Value Constraint. Select default or fixed value constraint in the dropdown list and specify the value in the adjacent field. Value constraint is optional.
5. Value Domain. See Edit Value Domain.
6. Definition Source. Specify the source of the definition. This is typically a URI, but the field is free form text. Definition Source is optional.
7. Definition. Specify the description of the SC. This is the definition of SC in the context of the DT. Definition is optional, but a warning is given if none is specified.
Click the “Update” button at the top right to accept changes.

Note that any changes to the SC are propagated to the corresponding SC in all DTs derived from this DT. Therefore, any restrictions put upon this SC will overwrite the restrictions in the derived DT. However, editing an SC in the derived DT will not effect the same SC in the based DT.

Remove a newly added SC from a DT¶

Only a newly added SC can be removed. SCs that are inherited from the based DT cannot be removed. Removing an SC in a DT will also result in the removal of the same SC in derived DTs.

On the DT detail page where the current user owns the DT and the DT is in WIP state, expand the root node on the DT tree.
Click on the ellipsis next to any SC of the DT, if logically allowed, the “Remove” menu item is visible and active, select the menu item.
Click “Ok” in the confirmation dialog box, or “Cancel”, if so desired.

Edit details of an existing SC¶

The section describes the case of editing an SC inherited from a based DT or when revising a DT. The DT can be either a brand-new (revision #1) or revised DT (revision greater than #1).

On the DT detail page where the current user owns the DT, and the DT is in WIP state, expand the root node on the DT tree.
Click on an SC node of the DT. The detail of the SC is displayed in the detail pane on the right side of the page.
1. Property Term. Property term cannot be changed.
2. Representation Term. The Representation Term cannot be changed.
3. Cardinality. Cardinality can be changed only if the current value is optional.
4. Value Constraint. Select default or fixed value constraint in the dropdown list and specify the value in the adjacent field. Value constraint is optional.
5. Value Domain. See Edit Value Domain.
6. Definition Source. Specify the source of the definition. This is typically a URI, but the field is free form text. Definition Source is optional.
7. Definition. Specify the description of the SC. This is the definition of SC in the context of the DT. Definition is optional, but a warning is given if none is specified.
Click the “Update” button at the top right to accept changes.

Note that any changes to the SC are propagated to the corresponding SC in all DTs derived from this DT. Therefore, any restrictions put upon this SC will overwrite the restrictions in the derived DT.

Delete a newly created DT¶

A DT whose revision number is 1 can be (marked) deleted. The DT has to be in the WIP state and owned by the current user. See Delete a newly created CC.

Restore a deleted DT¶

Revise a DT¶

A DT in the Published state can be revised where certain changes can be made. Any developer user can revise a published DT. He/she does not have to be its owner. To do that:

Find a DT in the Working branch.
Open detail page of a DT in the Published state.
Click the Revise button at the top-right corner of the page. The DT goes into the WIP state and its revision number increases by 1.
Only the following fields in the DT detail pane on the right may be updated.
1. Definition Source. Specify the source of the definition. This is typically a URI but the field accepts a free form text. Definition Source is optional.
2. Definition. Specify the description of the BCCP. Definition is optional, but a warning is given if none is specified.
3. Content Component Definition. Specify the definition of the DT’s Content Component value. This is typically a free form text. Content Component Definition is optional.
Click the “Update” button at the top right to save changes.
The developer may want to perform these other actions on the DT:

Cancel a DT revision¶

See Cancel a CC revision.

Change DT states¶

Transfer ownership of a DT¶

See Transfer ownership of a CC.

View history of changes to a DT¶

Common Developer CC Management Functions¶

The user guide in this section commonly applies to BCCP, ASCCP, and ACC.

Delete a newly created CC¶

A CC with revision #1 can be deleted. Doing so will put the CC into the deleted state. This signifies that the owner of the deleted CC does not want to use it anymore. It suggests that if the CC is used by another developer, he/she should consider using another CC. It is recommended that the owner documents the reason for deletion in the Definition field before deleting. Other developers (or the owner himself) can however restore the CC - See Restore a deleted CC. To delete a CC:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more CCs to delete. See Search and Browse CC Library for help in locating a CC.
There are two ways to delete a CC:
1. Delete one or more CCs simultaneously.
  1. Check the checkbox in front of one or more CCs that are in the WIP state, have revision 1, and owned by the current developer.
  2. A trash icon is displayed at the top-right corner of the page.
  3. Select the trash icon.
2. Delete a CC individually:
  1. Click on the DEN of the CC to open its detail page. The CC must be in the WIP state, has revision 1, and is owned by the current developer.
  2. Click the “Delete” button at the top-right corner.
Confirm (or cancel) the deletion on the pop-up dialog.

Restore a deleted CC¶

Once a CC has been deleted, the ownership is delinquent from the current owner. Any other developers can restore the CC to the WIP state and take the ownership. To restore a CC.

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more CCs to restore from deletion. See Search and Browse CC Library for help in locating a CC. There are two ways to restore a CC.
1. Restore one or more CCs simultaneously:
  1. Check the checkbox in front of the CCs that are in the Deleted state.
  2. A trash can with an arrow icon inside is displayed at the top-right corner of the page.
  3. Select the icon.
2. Restore CC individually:
  1. Click on the DEN of a deleted CC to open its detail page.
  2. Click the “Restore” button at the top-right corner of the page.
Confirm (or cancel) the restoration on the pop-up dialog.

Cancel a CC revision¶

The developer who is the owner of a CC being revised can cancel the revision. In this case, all changes to the CC are discarded. CC detail and its owner are rollbacked to the pre-revised state. To cancel a CC revision:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find the CC to cancel its revision. See Search and Browse CC Library for help in locating a CC.
Click on the DEN of the CC to open its detail page. The current user has to be the owner of the CC and the CC has to be the WIP state with revision number greater than 1.
Click the “Cancel” button at the top-right of the page.
Confirm (or cancel) the revision cancellation.

Change a CC state¶

The section covers the toggling between WIP, Draft, and Candidate CC states. For detailed meaning of these and other states, see CC States. The current user has to be the owner of the CC to toggle between these three states. To change the CC state:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more CCs to change the state. See Search and Browse CC Library for help in locating a CC.
There are two ways to change state of a CC:
1. Change the state of one or more CCs in one shot.
  1. Check the checkbox in front of one or more CCs that are in the same state and owned by the current developer.
  2. Arrow icons are displayed at the top-right corner of the page. Depending on the current state of the selected CCs; left, right, or both arrow icons are displayed.
  3. Click the left arrow icon to retract the state or click the right arrow icon to advance the state.
2. Change the state of CC individually:
  1. Open the CC detail page, clicking the DEN of the CC in WIP, Draft, or Candidate state that is owned by the current developer.
  2. Depending on the current state of the CC, click either the “Move to Draft”, “Move to Candidate”, or “Back to WIP” button at the top-right corner of the page.
3. Confirm (or cancel) the state change.

Transfer ownership of a CC¶

To let another developer makes changes to a CC, the current owner has to transfer ownership of the CC to another developer. Developer CC can be transferred only to another developer. To transfer ownership:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more CCs to transfer ownership. See Search and Browse CC Library for help in locating a CC.
There are two ways to transfer ownership of a CC:
1. Transfer ownership of one or more CCs simultaneously.
  1. Check the checkbox in front of one or more CCs that are owned by the current developer and are in the WIP state.
  2. The double-arrow icon is displayed at the top-right corner of the page.
  3. Click the double-arrow icon.
  4. A dialog is displayed to select a developer. Use the filter on the top to find the desired developer and check the checkbox in front of it.
  5. Click the “Transfer” button.
2. Transfer ownership of a CC individually:
  1. On the “Core Component” page, when a CC is in the WIP state and is owned by the current developer, there is a double-arrow icon next to the username of the owner.
  2. Click the double-arrow icon.
  3. A dialog is displayed to select a developer. Use the filter on the top to find the desired developer and check the checkbox in front of it.
  4. Click the “Transfer” button.

View Change History of a CC¶

On any CC detail page, click on the ellipsis of a node in the CC tree in the left pane. Select the “Show History” menu item.
A new browser tab is opened showing a list of changes that have occurred.
Check any two checkboxes in the list. The “Compare” button is activated.
Click the “Compare” button.
A diff dialog is open. Older copy is shown on the left and the newer one is shown on the right. Fields that were changed are highlighted in blue. Things that were newly added are highlighted green.
Click anywhere outside the dialog or hit the “Esc” key to close the diff dialog.

Purge a CC¶

Purge allows for permanently discarding CCs, Code Lists and Agency ID lists from Score. Such entities along with their logs and comments can never be restored back.

Any developer can purge any CC providing that it is in the Deleted state. See Delete a newly created CC. However, if the CC is still used by another CC (as a property, base, or role of an ASCCP) that is not in the Deleted state, it cannot be purged. For instance, if you want to purge a deleted BCCP which is still used as a property of an ACC. The ACC should be deleted first.

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more CCs to delete. See Search and Browse CC Library for help in locating a CC.
There are two ways to purge a CC:
1. Delete one or more CCs simultaneously.
  1. Check the checkbox in front of one or more CCs that are deleted.
  2. A trash icon with a “Purge” toolbox is displayed at the top-right corner of the page.
  3. Click this trash icon.
2. Delete a CC individually:
  1. Click on the DEN of the CC to open its detail page. The CC must be in the Deleted state.
  2. Click the “Purge” button at the top-right corner.
A confirmation dialog is displayed. Confirm or cancel the purge request.

Tagging CCs¶

The tagging feature in Score allows users to label and categorize core components for better management. With this feature, users can assign custom tags to core components making it easier to locate and work with them later. To label the tag to core components:

Click on the ellipsis of a node in the CC tree located in the left pane on any CC detail page.
Next, select the “Tag” option from the menu that appears.
1. To apply the tag to the core component, choose the desired tag from the list of available tags in the submenus.
2. To add a new tag, first click on the “Edit Tags” menu item. Then, scroll down to the bottom of the dialog box. Next, type in the “Name”, “Text Color”, “Background Color”, and “Description (Optional)” fields for the new tag. Finally, click on the “Add” button to create the new tag.
3. To edit existing tags, click on the “Edit Tags” menu item. Then, update the “Name”, “Text Color”, “Background Color”, and “Description (Optional)” fields of the tag. Finally, click on the “Update” button to save the changes.
4. To discard existing tags, click on the “Edit Tags” menu item and then click on the “Discard” button located below the tag properties.

Export ASCCPs¶

“Export ASCCPs” allows users to download the schema expression of the ASCCP(s) in XML. To export it:

Select the ASCCP(s) in the list by clicking the checkbox(es). The export icon button will appear on the upper right hand corner of the screen.
Click the export icon button.

Create an OAGIS BOD¶

Score includes a macro for creating an OAGIS BOD for a selected ASCCP. To create an OAGIS BOD:

Click on the “View/Edit Core Component” menu item under the “Core Component” menu, if you are not already on the “Core Component” page.
Click on the plus sign at the top-right of the page.
Select “Create OAGi BOD” Component.
A dialog opens up where a Verb can be selected on the left side and an ASCCP can be selected on the right side. Use the filters on the top find and select a Verb and an ASCCP. Multiple Verbs and multiple ASCCPs can be selected; and pairwise BODs will be created.
Click the “Create” button at the bottom of the page.
Four CCs are automatically created with appropriate structures and relationships. The tool opens the detail page of the ASCCP representing the BOD. It is more convenient to go back to the “Core Component” page to manage states the four CC altogether.

Note: Create OAGIS BOD macro needs some standard OAGIS CCs. If this macro is invoked when the database does not contain those CCs, it will fail.

Code List Management¶

Code list management has its own page. In Score, code lists created by Score developers are considered a kind of CC because they can be included in the release of standard Core Component. Therefore, the Code List Management functionality can be accessed under the “Core Component” menu.

Find a code list¶

To find a code list needed to work on, select “View/Edit Code List” under the “Core Component” menu on the top of Score pages. The “Code List” page is open that contains a table listing all code lists in a particular branch. To manage developer code lists, ensure that Working is selected in the Branch filter. Use search filters on the top of the table to find the desired code list. All filters on the Code List have the same meaning as those described in How to Search and Filter for a Core Component, except that some filters do not exist on the Code List page and the Code List page has Name instead of DEN. The CC Specification does not have Code List as one of the Registry Classes and hence Code List does not have DEN specification. Name of the code list a free form text.

View detail of a code list¶

To view code list detail:

Find a code list.
Click on the code list name to open the Edit Code List page. Note: clicking somewhere else on a code list entry will display its textual definition.

Create a new code list¶

To create a brand-new code list.

Open the “Code List” page by selecting “View/Edit Code List” under the “Core Component” menu on the top of Score pages.
Ensure that “Working” is selected in the Branch filter.
Click the “New Code List” button at the top-right of the page.
Detail of the code list can be updated including add/change code list values.

Edit detail of a brand-new code list¶

This section describes code list editing when its revision number is 1.

Make sure you are on the Working branch. Open the Edit Code List detail page according to View detail of a code list. The code list has to be in the WIP state, and the current user has to be the owner to be editable. The fields in the detail pane may be updated as follows.
1. Name. It is the name of the code list. The value should be space-separated set of words. Acronyms and plural words should be avoided. Name is required.
2. List ID. This is a free form text representing external/global identifier of the code list. It is defaulted with a uniquely generated GUID, but it can be changed. List ID is required.
3. Agency ID List and Agency ID List Value. This combination of this two fields represents an organization that owns and manages the code list. Currently, only one developer Agency ID List is allowed in a release, so there is always only one in the Agency ID List dropdown Select an Agency ID from the Agency ID List value drop down. If there is no desired agency ID value in the list, revise the developer Agency ID List and add a new value. These two fields are required.
4. Version. This field is a freeform text representing the version of the code list. The system will validate the combination of List ID, Agency ID, and Version is unique in the (working) branch data. Version is required.
5. Namespace. Select a standard namespace from the dropdown list. See the Namespace Management section to create a standard namespace if needed or how namespace may be used in Score. Namespace is required.
6. Definition. Specify the description of the code list. Definition is optional, but a warning is given if none is specified.
7. Definition Source. Specify the source of the definition. This is typically a URI, but the field is free form text. Definition Source is optional.
8. Deprecated. The Deprecated checkbox is only applicable when the code list revision is higher than 1. Therefore, the field is locked.
Click the “Update” button at the top right to save changes.
The developer may also want to perform these other actions on the code list:

Add a brand-new code list value to the code list¶

A code list value can be added to a code list that is in WIP state and is owned by the current user.

At the bottom of the “Edit Code List” page, click the “Add” button.
A dialog pops up where the following fields can be edited.
1. Code. The code value to be used in the message instance. Code is required.
2. Meaning. Short name or short description of the code value. Meaning is required.
3. Definition. Long description of the code value. Definition is optional.
4. Definition Source. The source of the definition. This can be any text but usually a URI is specified. It is optional.
5. Deprecated. The checkbox is disabled when a code value is newly added.
6. For example, Code is “YYYY-MM-DDThh:mm:ssZ”, Meaning is “UTC Date and Time”, Definition is “ISO 8601 Date and Time extended format: YYYY-MM-DDThh:mm:ssZ with optional fraction of second allowed (YYYY-MM-DDThh:mm:ss,ssZ)”.
Click the “Add” button at the bottom of the dialog. To get out of the dialog without adding the code value, hit the ESC button or click outside of the dialog.
Click the “Update” button at the top of the page.

Remove a brand-new code list value from the code list¶

A code list value can be removed from a code list only when it is newly added to a brand-new code list or to a revised code list. The code list must be in the WIP state and is owned by the current user.

In the “Code List Values” table on the “Edit Code List” page, click the checkboxes in front of one or more code list values intended to be deleted. Only removable code list values have their checkboxes enabled.
Click the “Remove” button at the bottom of the page.
A confirmation dialog is displayed. Confirm or cancel the removal request.
Click the “Update” button at the top of the page.

Edit detail of a brand-new code list value¶

This section describes the case when the code list value is brand-new, i.e., a code list value added to a revision 1 code list (brand-new code list) or to a revised code list (revision number more than 1). The code list must be in the WIP state and is owned by the current user. To edit the detail of a code list value:

In the Code List Values table on the “Edit Code List” page, click on the row of the code list value to be updated.
The “Edit Code List Value” dialog is open. Detail of the code list value can be updated as described in Add a brand-new code list value to the code list.
Click the “Save” button at the bottom of the dialog. To get out of the dialog without saving the changes, hit the ESC button or click outside of the dialog.
Click the “Update” button at the top of the page.

Revise a code list¶

A developer code list in the Published state can be revised. The current user does not have to be the owner of the code list. To revise a code list:

Make sure you are on the Working branch. Open the “Edit Code List” page of a code list in the Published state.
Click the “Revise” button at the top-right corner of the page.
The “Edit Code List” page is refreshed with the code list whose revision number is incremented by 1.
Detail of the code list can be updated including add/change code list values.

Edit detail of a revised code list¶

This section describes code list editing when its revision number is 2 or more.

Open the “Edit Code List detail” page according to View detail of a code list. The code list has to be in the WIP state, and the current user has to be the owner to be editable. The fields in the detail pane may be updated as follows:
1. Name. It is the name of the code list. The field is locked and not editable.
2. List ID. This is a free form text representing external/global identifier of the code list. The field is locked, and change is not allowed.
3. Agency ID List and Agency ID List Value. This combination of these two fields represents an organization that owns and manages the code list. These fields are locked, and change is not allowed.
4. Version. This field is a freeform text representing the version of the code list. The system will validate the combination of List ID, Agency ID, and Version is unique in the (working) branch data. Version is required. The field can be changed
5. Namespace. The field is locked and cannot be changed.
6. Definition. Specify the description of the code list. Definition is optional but a warning is given if none is specified.
7. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts a free form text. Definition Source is optional.
8. Deprecated. The deprecated checkbox allows the code list to be marked for deprecation.
Click the “Update” button at the top-right of the page to save changes.
The developer may also want to perform these other actions on the code list:

Revise detail of a code list value¶

This section describes the case when the code list value has existed since the previous revision of the code list. To revise the detail of a code list value:

In the Code List Values table on the “Edit Code List” page of a code list with revision number 2 or more, click on the row of the code list value to be updated.
The “Edit Code List Value” dialog is open. Detail of the code list value can be updated as follows.
1. Code. Change is not allowed.
2. Meaning: Change is allowed and the field is mandatory.
3. Definition: Long description of the code value. Definition is optional.
4. Definition Source: The source of the definition. This can be any text but usually a URI is specified. It is optional.
5. Deprecated: Check the check box to deprecate the code list value.
Click the “Save” button at the bottom of the dialog. To get out of the dialog without saving the changes, hit the ESC button or click outside of the dialog.
Click the “Update” button at the top of the page.

Delete a brand-new code list¶

A code list with revision #1 can be deleted. Doing so will put the code list into the deleted state. This signifies that the owner of the deleted code list no longer wants to use it. This suggests that if the code list is used by another developer in another CC, he/she should consider using another code list. It is recommended that the owner documents the reason for deletion in the Definition field before deleting. Other developers (or the owner himself) can however restore the code list - see Restore a deleted code list. To delete a code list:

Go to the “Code List” page by clicking the “View/Edit Core List” menu item under the “Core Component” menu. Find one or more Code Lists to delete. Make sure you are on the Working Branch. See Find a code list for help in locating a code list.
There are two ways to delete a code list:
1. Delete one or more code lists simultaneously.
  1. Check the checkbox in front of the code lists that are in the WIP state, have revision 1, and are owned by the current developer.
  2. The “Delete” button on top-right corner of the page is activated.
  3. Click the “Delete” button.
2. Delete code list individually
  1. Click on the ellipsis in the last column of the code list entry. The code list must be in the WIP state, has revision 1, and is owned by the current developer. Click the “Delete” menu item in the pop-up menu.
  2. Alternatively, click the code list name to open its detail page and click the “Delete” button at the top-right corner of the page.
Confirm (or cancel) deletion on the pop-up dialog.

Restore a deleted code list¶

Once a code list has been deleted, the ownership is delinquent from the current owner. Any other developers can restore the code list to the WIP state and take the ownership. To restore a code list.

Go to the “Code List” page by clicking the “View/Edit Code List” menu item under the “Core Component” menu. Find one or more code lists to restore from deletion. See Find a code list for help in locating a code list. There are two ways to restore a code list.
1. Restore one or more code lists simultaneously:
  1. Check the checkbox in front of the code lists that are in the Deleted state.
  2. A “Restore” button is activated at the top-right corner of the page.
  3. Click the “Restore” button.
2. Restore code list individually:
  1. Click on the ellipsis in the last column of the code list entry that is in the Deleted state. Click the “Restore” menu item in the pop-up menu.
  2. Alternatively, click on the name of a deleted code list to open its detail page and click the “Restore” button at the top-right corner of the page.
Confirm (or cancel) restoration on the pop-up dialog.

Cancel a code list revision¶

The developer who is the owner of a code list being revised can cancel the revision. In this case, all changes to the code list are discarded. Code list detail and its owner are rollbacked to the pre-revised state. To cancel code list revision:

Go to the “Code List” page by clicking the “View/Edit Code List” menu item under the “Core Component” menu. Find a code list to restore from deletion. Make sure you are on the Working Branch. See Find a code list for help in locating a code list.
Click on the name of the code list to open its detail page. The current user has to be the owner of the code list and the code list has to be the WIP state with a revision number greater than 1.
Click the “Cancel” button at the top-right of the page.
Confirm (or cancel) the revision cancellation.

Change a code list state¶

The section covers the toggling between WIP, Draft, and Candidate states of the code list. For the detailed meaning of these and other states, see Change a CC state. The current user has to be the owner of the code list to toggle between these three states. To change the code list state:

Go to the “Code List” page by clicking the “View/Edit Code List” menu item under the “Core Component” menu. Find a code list to work on. Make sure you are on the Working Branch. See Find a code list for help in locating a code list.
Click on the name of the code list to work on.
Depending on the current state of the code list, click either the “Move to Draft”, “Move to Candidate”, or “Back to WIP” button at the top-right corner of the page.
Confirm (or cancel) the state change.

Transfer ownership of a code list¶

To let another developer makes changes to a code list, the current owner has to transfer ownership of the code list to another developer. Developer code lists can be transferred only to another developer. To transfer ownership:

Go to the “Code List” page by clicking the “View/Edit Code List” menu item under the “Core Component” menu. Find a code list to transfer ownership. Make sure you are on the Working Branch. See Find a code list for help in locating a code list.
There are two ways to transfer ownership of a code list:
1. Click the transfer icon (icon with two opposite arrows) next to the owner of the code list, or
2. Click on the ellipsis in the last column of the code list to transfer the ownership and select “Transfer Ownership” menu item in the pop-up menu.
A dialog is displayed to select a developer. Use the filter on the top to find the desired developer and check the checkbox in front of it.
Click the “Transfer” button.

Agency ID List Management¶

Agency ID List management has its own page which can be accessed under the “Core Component” menu. In Score, there is only one Agency ID List created by the default account, namely, “oagis”. The current design does not allow developer users to create a new Agency ID List. The idea is the agency ID is one of the lowest common denominators in a standard that facilitate interoperability and having more than one agency ID Lists does not help. In the future, this restriction will be lifted to either allow one to be created if none exists or allow many to be created. Developers however can revise the existing Agency ID List to add new values and include it in the next release of Core Components. In Score, Agency ID Lists are considered a kind of CC because they can be included in the release of standard Core Components.

Find an Agency ID List¶

To find an Agency ID List needed to work on, select “View/Edit Agency ID List” under the “Core Component” menu on the top of Score pages. The “Agency ID List” page is open that contains a table listing the Agency ID List in a particular branch. To manage the existing Agency ID List, ensure that Working is selected in the Branch filter. There are also search filters on the top of the table to use but there is no need since there is only one developer Agency ID List. Developers can use these filters when a non-working release is selected in the Branch filter. All filters on the Agency ID List have the same meaning as those described in How to Search and Filter for a Core Component, except that some filters do not exist on the Agency ID List page and the Agency ID List page has Name instead of DEN. The CC Specification does not have Agency ID List as one of the Registry Classes and hence Agency ID List does not have a DEN specification. Name of the Agency ID List a free form text.

View detail of an Agency ID List¶

To view Agency ID List detail:

Find an Agency ID List.
Click on the Agency ID List name to open the Edit Agency ID List page. Note: clicking somewhere else on an Agency ID List entry will display its textual definition.

Create a new Agency ID List¶

Developers cannot create a new Agency ID List. In case a change is needed, developers should revise the existing Agency ID List (see Revise an Agency ID List)

Revise an Agency ID List¶

A developer Agency ID List in the Published state can be revised. The current user does not have to be the owner of the Agency ID List. To revise an Agency ID List:

Make sure you are on the Working branch. Open the “Agency ID List” page of an Agency ID List in the Published state.
Click the “Revise” button at the top-right corner of the page.
The “Edit Agency ID List” page is refreshed with the Agency ID List whose revision number is incremented by 1.
Detail of the Agency ID List can be updated including add/change Agency ID List values.

Edit detail of a revised Agency ID List¶

This section describes Agency ID List editing when its revision number is 2 or more.

Open the “Edit Agency ID List detail” page according to View detail of an Agency ID List, if it is not already opened. The Agency ID List has to be in the WIP state, and the current user has to be the owner to be editable. The fields in the detail pane may be updated as follows:
1. Name. It is the name of the Agency ID List. The field is locked and not editable.
2. List ID. This is a free form text representing external/global identifier of the Agency ID List. The field is locked, and change is not allowed.
3. Agency ID. This field represents the organization that owns and manages the Agency ID List. The field is locked, and change is not allowed.
4. Version. This field is a freeform text representing the version of the Agency ID List. The system will validate the combination of List ID, Agency ID, and Version is unique in the (working) branch data. However, there is only one Agency ID List allowed at this time, so this is always valid. Although the version should generally be different from prior revisions, Score does not validate this. Version is required.
5. Namespace. The field is locked and cannot be changed.
6. Definition. Specify the description of the Agency ID List. Definition is optional but a warning is given if none is specified.
7. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts a free form text. Definition Source is optional.
Click the “Update” button at the top-right of the page to save changes.
The developer may also want to perform these other actions on the Agency ID List:

Add a brand-new Agency ID List value to the Agency ID List¶

An Agency ID List value can be added to an Agency ID List that is in WIP state and is owned by the current user.

At the bottom of the “Edit Agency ID List” page, click the “Add” button.
A dialog pops up where the following fields can be edited.
1. Value. The value of the Agency ID List value. Value is required.
2. Meaning. Short name or short description of the Agency ID List value. Meaning is required.
3. Definition. Long description of the Agency ID List value. Definition is optional.
4. Definition Source. The source of the definition. This can be any text but usually a URI is specified. It is optional.
5. Deprecated. The checkbox is disabled when a code value is newly added.
Click the “Add” button at the bottom of the dialog. To get out of the dialog without adding the Agency ID List value, hit the ESC button or click outside of the dialog.
Click the “Update” button at the top of the page.

Remove a brand-new Agency ID List value from the Agency ID List¶

An Agency ID List value can be removed from an Agency ID List only when it is newly added to the revised Agency ID List and it is not used in a Code List. The Agency ID List must be in the WIP state and is owned by the current user.

In the “Agency ID List Values” table at the bottom of the “Edit Agency ID List” page, click the checkboxes in front of one or more Agency ID List values intended to be removed. Only removable Agency ID List values have their checkboxes enabled.
Click the “Remove” button at the bottom of the page.
A confirmation dialog is displayed. Confirm or cancel the removal request.
Click the “Update” button at the top of the page.

Edit detail of a brand-new Agency ID List value¶

This section describes the case when the Agency ID List value is brand-new, i.e., an Agency ID List value added to a revision 1 Agency ID List (brand-new Agency ID List) or to a revised Agency ID List (revision number more than 1). The Agency ID List must be in the WIP state and is owned by the current user. To edit the detail of an Agency ID List value:

In the “Agency ID List Values” table on the “Edit Agency ID List” page, click on the row of the Agency ID List value to be updated.
The “Edit Agency ID List Value” dialog is open. Detail of the Agency ID List value can be updated as described in Add a brand-new Agency ID List value to the Agency ID List.
Click the “Save” button at the bottom of the dialog. To get out of the dialog without saving the changes, hit the ESC button or click outside of the dialog.
Click the “Update” button at the top of the page.

Revise detail of an Agency ID List value¶

This section describes the case when the Agency ID List value has existed since the previous revision of the Agency ID List. To revise the detail of an Agency ID List value:

In the Agency ID List Values table at the bottom of the “Edit Agency ID List” page where the revision number of the Agency ID List is 2 or more, click on the row of the Agency ID List value to be updated.
The “Edit Agency ID List Value” dialog is open. Detail of the code list value can be updated as follows.
1. Value. Change is not allowed.
2. Meaning: Change is allowed, and the field is mandatory.
3. Definition: Long description of the Agency ID List value. Definition is optional.
4. Definition Source: The source of the definition. This can be any text but usually a URI is specified. It is optional.
5. Deprecated: Check the check box to deprecate the Agency ID List value.
Click the “Save” button at the bottom of the dialog. To get out of the dialog without saving the changes, hit the ESC button or click outside of the dialog.
Click the “Update” button at the top of the page.

Delete a brand-new Agency ID List¶

Developers cannot delete the existing Agency ID List since it is published. They cannot either delete the revision of this Agency ID List since a revised CC cannot be deleted.

Cancel an Agency ID List revision¶

The developer who is the owner of the Agency ID List being revised can cancel the revision. In this case, all changes to the Agency ID List are discarded. Agency ID List detail and its owner are rollbacked to the pre-revised state. To cancel Agency ID List revision:

Open the “Edit Agency ID List” page of an Agency ID List that is not in the Published state and with revision number greater than 1 (i.e., a revised Agency ID List). The current user must be the owner of the Agency ID List.
If it is not in the WIP state change the state back to WIP.
Click the “Cancel” button at the top-right of the page.
Confirm (or cancel) the revision cancellation.

Change an Agency ID List state¶

The section covers the toggling between WIP, Draft, and Candidate states of the Agency ID List. For the detailed meaning of these and other states, see Change a CC state. The current user has to be the owner of the Agency ID List to toggle between these three states. To change the Agency ID List state:

Open the “Edit Agency ID List” page of an Agency ID List that is not in the Published state and with revision number greater than 1 (i.e., a revised Agency ID List). The current user has to be the owner of the Agency ID List. Also, make sure you are on the Working Branch.
Depending on the current state of the Agency ID List, click either the “Move to Draft”, “Move to Candidate”, or “Back to WIP” button at the top-right corner of the page.
Confirm (or cancel) the state change.

Transfer ownership of an Agency ID List¶

To let another developer makes changes to an Agency ID List, the current owner has to transfer ownership of the Agency ID List to another developer. Developer Agency ID Lists can be transferred only to another developer. To transfer ownership:

Go to the “Agency ID List” page by clicking the “View/Edit Agency ID List” menu item under the “Core Component” menu. There is only one developer Agency ID List. Make sure you are on the Working Branch.
There are two ways to transfer ownership of an Agency ID List:
1. Click the transfer icon (icon with two opposite arrows) next to the owner of the Agency ID List, or
2. Click on the ellipsis in the last column of the Agency ID list to transfer the ownership and select “Transfer Ownership” menu item in the pop-up menu.
A dialog is displayed to select a developer. Use the filter on the top to find the desired developer and check the checkbox in front of it.
Click the “Transfer” button.

Release Management¶

Overview of release management process¶

A release lifecycle consists of 3 stages including 1) Initialized, 2) Draft, 3) Published. Only developers can manage releases. Release does not have an owner; therefore, after a release has been created, any developer can manage the release. Figure below shows the lifecycle state transitions.

There may be multiple releases in the Initialized state. This can help with release planning. High-level scope of the release can be captured in the release note.

Only one release draft can be active at any point in time. In other words, if there is a release draft in the system, another release draft cannot be created. The release draft allows the standard development team/community to review the changes to the release and the release itself as a whole. Once the review period is over, if some changes are needed the release draft has to be first canceled, and then all changes to CCs (recall that CCs also include developer code lists and agency identifier list) assigned to the draft can be updated again. The release may move back and forth between the Initialized and Draft state until all comments are satisfactorily addressed. Once that is the case, the release can be published, and it is moved to the Published state. In the published state, the release information can no longer be changed.

A release in the Initialized state can be discarded. In such case, the release is purged from the application and can never be restored back.

Find a release¶

To find a release:

On the “Core Component” menu on the top, click the “View/Edit Release” menu item.
The “Release” page is open listing all the releases.
Use the pagination buttons on the bottom of the release table to find the desired release. Use the “Items per page” to display more or fewer releases per page. Alternatively, use the filters described below to search for the desired release. When multiple filters are specified, they are connected with the AND logical connector. When they are not specified, they are not considered.
1. Creator. Select from the dropdown list the developer who created the release. The user can type in a few characters to narrow down the list.
2. Created start date and Created end date. Specify the time period in which the release was created by using Created end date and/or Created end date fields.
3. Updated start date and Updated end date. Specify the time period in which the release was updated by using the Updated start date and/or Updated end date fields.
4. Updater. Select from the dropdown list the developer who last updated the release. The user can type in a few characters to narrow down the list.
5. Release Num. Type in a free form text to do a string match with the release number. Note that despite its name, the release number is actually a free text field, not just a number.
6. State. Select from the dropdown list the Initialized, Draft, or Published. Multiple states can be selected. If nothing is selected, all states are included, i.e., it is the same as selecting all of them.

Create a release¶

To create a new release:

On the “Core Component” menu on the top, click the “View/Edit Release” menu item.
The “Release” page is open.
Click the “New Release” button at the top-right of the page.
The following fields can be filled in.
1. Release Number. A freeform text representing the release number such as “10.0” or “10.0rc”. Release number should be unique within the database, although the application does not enforce it. Release Number is required.
2. Release Namespace. Select from the dropdown list a Standard Namespace. See also Namespace Management. Release Namespace is required.
3. Release Note. A freeform text that describes or gives an overview of the release. The field is optional.
4. Release License. A freeform text indicating the licensing of the CC release. The field is optional.
Click the “Create” button.
The “Release” page opens showing the created release in the Initialized state.

View detail of a release¶

Find a release.
Click on the release number to open the release detail page.

Edit detail of a release¶

Detail of a release can be edited while it is in the Initialized or Draft state. Any developer can edit the detail of a release. He/she does not have to be the owner. To change the detail of a release:

Open the detail page of the release.
Fields of the release detail can be updated in the same way as when the release was first created.

Create a release draft¶

In the release draft creation process, CCs in the candidate state can be assigned to a release that is in the initialized state. Any developer can create a release draft from a release in the Initialized state. He/she does not have to be the owner. To create a release draft:

Open the detail page of a release that is in the Initialized state and click the “Create Draft” button at the bottom of the page. Alternatively, open the “Release” page by clicking “View/Edit Release” under the “Core Component” menu. Then, click on ellipsis in the last column of the desired initialized release and select “Create Draft”.
The “Release Assignment” page is open. The page has two panes left and right. The left, aka Modified pane, has all the CCs (recall that CCs also include code and agency identifier lists) created/changed in the Working branch. The right, aka Assigned pane, contains CCs assigned to the release and is initially empty.
Assign CCs to the release by selectively dragging CCs that are in the Candidate state from the left pane to the right pane. Alternatively, use the double-arrowhead icon (>>) on the top of the left pane to assign all CCs in the Candidate state. CCs on the right pane can also be dragged back to the left pane to unassign.
After all new and updated CCs planned for the release have been assigned,
1. Click the “Validate” button at the bottom of the page. This step is optional. If there is any error such as when some CCs used by CCs assigned to the release are not included in the release, error messages are displayed. Warnings are also given for certain situations such as updated CCs that are not assigned to the release.
2. Click the “Create” button at the bottom of the page. If the release assignment has not been validated, the system validates the assignment. If there is any error, draft is not created. If there is no error, the system starts the process to create the release draft.
The “Release” page is open showing that the release draft is being created – the State column is shown as Processing. If there are not hundreds of new or changed CCs, the release draft processing can finish in few seconds. The page is NOT automatically refreshed when the processing is done. The user has to refresh the page to see whether the processing is done. When that is the case, the State column will display Draft. At this stage, the user may go to the “Core Component” page and on the Branch filter at the top-left of the page select the release draft from the list to review all CCs in the release draft. The user may also want to notify other developers or end users that the release draft is ready for review.

Review a release draft¶

Once a release draft has been created, users, both developers and end users, can review the release. To do so:

Open the “Core Component” page by clicking the “Core Component” menu on the top and selecting “View/Edit Core Component”.
In the Branch filter at the top-left of the page, select a branch with the Release Draft label and click the “Search” button under search filters.
CCs in the release draft are listed. There should be CCs in only two states, Release Draft and Published. The published ones are those CCs with no change from the previous release. The release draft ones are those CCs that are either new or revised in the release draft.
Use other filters as described in Search and Browse CC Library.
Click on the DEN of a CC to open its detail page. See all View Change History of a CC.
If changes to any CCs in the release draft are needed, the release draft has to be cancelled first.

Discard a release¶

A release in the Initialized state can be discarded. In such case, the release is purged from the application and can never be restored back. To discard a release:

Open the “Release” page by clicking “View/Edit Release” under the Core Component menu on the top.
Find a release to be discarded.
Click on the ellipsis in the last column of the release to be discarded and select “Discard”.
Confirm (or Cancel) the request on the confirmation dialog.

Cancel a release draft¶

If changes to any CC in the release draft are needed, the release draft needs to be canceled first. The cancellation frees CCs from the release and puts those ones with changes back to the Candidate state. CCs that need modification can then be put back in the WIP state to make further changes.

Open the “Release” page by clicking “View/Edit Release” under the “Core Component” menu on the top.
Find a release that is the Release Draft state that is to be canceled.
Click on the ellipsis in the last column of the release draft and select “Move back to Initialized”. Alternatively, click the release number to open the detail page and click the “Move back to Initialized” button.
A dialog appears to confirm or cancel the release draft cancellation.

Publish a release¶

After a release draft has been reviewed and accepted, it can be published. Any developer can publish a release draft. He/she does not have to be the owner. No further changes can be made to the release after it is published. To publish a release draft:

Open the “Release” page by clicking “View/Edit Release” under the “Core Component” menu at the top of the Score page.
There are two ways to publish a release:
1. If there is no need to update any release detail, the release can be published by clicking on the ellipsis in the last column of the release draft and selecting “Move to Published”. Click “Update” in the confirmation dialog. It is important to note that release detail cannot be changed after the release is published.
2. If there is a need to update some release detail:
  1. Open the detail page of the release that is in the Release Draft state.
  2. Release detail can be updated in the same way as when the release was first created.
  3. Click the “Publish” button.
  4. Click “Update” in the confirmation dialog.
The “Release” page opens showing that the release is being published – the State column is shown as Processing. If there are not hundreds of new or changed CCs, the publish processing can finish in few seconds. The page is NOT automatically refreshed when the processing is done. The user has to refresh the page to see whether the processing is done. When that is the case the State column will display Published. At this stage, the user may go to the “Core Component” page and on the Branch filter at the top-left of the page select the release from the list to see all CCs in the published release.

Generate the migration script¶

After a new release has published, developers can download the migration script for the new release. The script contains all developer records, including core components, code lists, agency ID lists, modules, etc. To download the script,

Open the detail page of the new release.
Click the “Generate Migration Script” button.

End user core component management¶

Score allows end users to create their Core Component and use them during the BIE extension. That is, users are not limited to using existing, standard CCs but also user-defined Core Components.

To manage end user core components, make sure that a published release branch (i.e., a non-working branch) is selected on the Core Component page.

Non-standard Namespace Management¶

All EUCCs require a Non-standard namespace (i.e., end user namespace). Standard Namespaces (i.e., developer namespace) cannot be used in an EUCC.

An end user can create and edit a Namespace he/she owns. He/she can also find and view the details of a Namespace. Finally, he can discard a Namespace or transfer the ownership of a Namespace to another user. It should be noted that the transfer of the ownership of a Non-standard namespace can occur only between end users.

BCCP Management¶

Find a BCCP¶

See Search and Browse CC Library to find the BCCP needed. For more information about finding a BCCP see also Find a BCCP. Make sure you are on a published release branch for EUCC.

View detail of a BCCP¶

See View detail of a BCCP.

Create a new BCCP¶

To create a new end user BCCP see Create a new BCCP.

Edit detail of a BCCP¶

To edit an end user BCCP please see Edit detail of a BCCP.

Important! when an end user is editing the details of a BCCP, only Non-standard Namespaces can be selected in the Namespace dropdown list. See the Non-standard namespace Management section to create a Non-standard namespace if needed or the Namespace Management section about the namespace use in Score.

Delete a newly created BCCP¶

See Delete a newly created EUCC.

Restore a deleted BCCP¶

Amend a BCCP¶

An end user BCCP in Production state can be amended where certain backwardly-compatible changes be made. Any end user can amend a production BCCP. He/she does not have to be its owner. To do that:

Find a BCCP in the desired published Release branch.
Open detail page of the BCCP.
Click the Amend button at the top-right corner of the page. The BCCP goes into the WIP state and its revision number increases by 1.
The following fields can be updated.
1. Nillable. It can only be updated from false (unchecked) to true (checked).
2. Deprecated. It can only be updated from false (unchecked) to true (checked).
3. Value Constraint. Select default or fixed value constraint in the dropdown list and specify the value in the adjacent field. Note that fixed value constraint and nillable are mutually exclusive, i.e., nillable cannot be true if there is a fixed value constraint and vice versa. Value constraint is optional.
4. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts a free form text. Definition Source is optional.
5. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.

Cancel a BCCP amendment¶

Change BCCP states¶

Transfer ownership of a BCCP¶

View history of changes to a BCCP¶

See View Change History of an EUCC.

ASCCP Management¶

Find an ASCCP¶

See Search and Browse CC Library to find the ASCCP needed. For more information about finding an ASCCP see Find an ASCCP. Make sure you are on a published release branch for EUCC.

View detail of an ASCCP¶

See View detail of an ASCCP.

Create a new ASCCP¶

There are two ways to create a new ASCCP.

Create an ASCCP from scratch.
1. If you are not already on, open the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu at the top of the page. Make sure that a published release branch is selected on top-left Branch dropdown list.
2. Click on the plus sign near the top-right corner of the page.
3. Select ASCCP.
4. The ACC selection page is open. Check the check box in front of the desired ACC. The user can use other search filters to find the desired ACC. Certain types of ACCs are excluded from the list including Extension, User Extension Group, Embedded, OAGIS10 Nouns, OAGIS10 BODs, For explanation about these different types in Score see Component Types.
5. A new ASCCP is created with revision #1. Its detail page is open with default values populated. The new ASCCP is in the WIP state. The end user may edit the detail of the ASCCP.
Create an ASCCP from an ACC.
1. Open the detail page of an ACC where the current user is the owner of the ACC and the ACC is in the WIP state.
2. Click the ellipsis next to the root node of the ACC tree in the left pane.
3. Select “Create ASCCP from this” menu item.
4. An ASCCP is created with default values. In this case, the property term is defaulted to the same as the ACC’s object class term. The end user may edit the detail of the ASCCP.

Edit detail of an ASCCP¶

To edit an ASCCP please see Edit detail of an ASCCP.

Important! when an end user is editing the details of an ASCCP, only Non-standard Namespaces can be selected in the Namespace dropdown list. See the Non-standard namespace Management section to create a Non-standard namespace if needed or the Namespace Management section about the namespace use in Score.

Delete a newly created ASCCP¶

See Delete a newly created EUCC.

Restore a deleted ASCCP¶

Amend an ASCCP¶

An ASCCP in the Production state can be amended in order to make certain backwardly-compatible changes. Any end user can amend a production ASCCP. He/she does not have to be its owner. To do that:

Find an ASCCP in a published Release branch.
Open detail page of an ASCCP.
Click the “Amend” button at the top-right corner of the page. The ASCCP goes into the WIP state and its revision number increases by 1.
The following fields can be updated.
1. Nillable. It can only be updated from false (unchecked) to true (checked).
2. Deprecated. It can only be updated from false (unchecked) to true (checked).
3. Reusable. It can only be updated from false (unchecked) to true (checked). If the reusable is changed to true, it means that there can be multiple ASCCs using the ASCCP. However, it may cause release invalidation if this results in multiple reusable ASCCP with the same property term.
4. Definition Source. Specify the source of the definition. This is typically a URI but the field accepts free form text. Definition Source is optional.
5. Definition. Specify the description of the ASCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.

Cancel an ASCCP amendment¶

Change ASCCP states¶

See Change EUCC states.

Transfer ownership of an ASCCP¶

View history of changes to an ASCCP¶

ACC Management¶

Find an ACC¶

See Search and Browse CC Library to find the ACC needed. For more information about finding an ACC see Find an ACC. Make sure you are on a published release branch for EUCC.

View detail of an ACC¶

See View detail of an ACC.

Create a new ACC¶

See Create a new ACC.

Edit detail of an ACC¶

To edit an ACC please see Edit detail of an ACC.

Important! when an end user is editing the details of an ACC, only Non-standard Namespaces can be selected in the Namespace dropdown list. See the Non-standard namespace Management section to create a Non-standard namespace if needed or the Namespace Management section about the namespace use in Score

Set a based ACC¶

See Set a based ACC.

Remove the based ACC¶

See Remove the based ACC.

Add a property to an ACC¶

See Add a property to an ACC.

Remove a property from an ACC¶

See Remove a property from an ACC.

Edit details of a new ASCC¶

See Edit details of a new ASCC.

Edit details of a new BCC¶

See Edit details of a new BCC.

Order the properties/associations¶

See Order the properties/associations.

Delete a newly created ACC¶

An ACC whose revision number is 1 can be (marked) deleted. The ACC has to be in the WIP state and owned by the current user. See Delete a newly created EUCC.

Restore a deleted ACC¶

Amend an ACC¶

An ACC in Production state can be amended where certain backwardly-compatible changes can be made. Any end user can amend a production ACC. He/she does not have to be its owner. To do that:

Find an ACC in a published Release branch.
Open the detail page of an ACC in Production state.
Click the “Amend” button at the top-right corner of the page. The ACC goes into the WIP state and its revision number increases by 1.
Only the following fields in the ACC detail pane on the right may be updated.
1. Deprecated. This can only be updated from false (unchecked) to true (checked). In other words, if the ACC was deprecated in the previous revision, it cannot be un-deprecated.
2. Definition Source. Specify the source of the definition. This is typically a URI, but the field accepts a free form text. Definition Source is optional.
3. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
Click the “Update” button at the top right to save changes.
The end user may want to perform these other actions on the ACC:
1. Set another ACC as a base of this ACC.
2. Remove the based ACC.
3. Add a property to the ACC and edit the detail of the resulting BCC or ASCC.
4. Remove a property from the ACC. Only the ASCC and BCC that are in revision 1 (i.e., added during the current revision) can be removed.
5. Order (i.e., change the sequence) the properties/associations.
6. Change the state of the ACC.
7. Create an ASCCP from this ACC.

Refactor a property to a based ACC¶

End users cannot refactor a property to a based ACC which is owned by developers. They can only refactor properties to a based ACC belonging to end users only. Everything else is the same as detailed in Refactor a property to a based ACC.

Cancel an ACC amendment¶

Change ACC states¶

See Change EUCC states.

Transfer ownership of an ACC¶

View history of changes to an ACC¶

See View Change History of an EUCC.

DT Management¶

A non-working branch should be selected in order for the end users to manage end-user DTs.

Find a DT¶

See Find a DT.

View detail of a DT¶

See View detail of a DT.

Create a new DT¶

See Create a new DT.

Edit detail of a DT¶

See Edit detail of a DT. Note that for the Namespace field of an end-user DT, a non-standard namespace should be selected. See the Non-standard Namespace Management section to create a non-standard namespace if needed or how namespace may be used in Score

Edit Value Domain¶

See Edit Value Domain.

Add an SC to a DT¶

See Add an SC to a DT.

Edit details of a new SC¶

See Edit details of a new SC.

Remove a newly added SC from a DT¶

See Remove a newly added SC from a DT.

Edit details of an existing SC¶

See Edit details of an existing SC.

Delete a newly created DT¶

A DT whose revision number is 1 can be (marked) deleted. The DT has to be in the WIP state and owned by the current user. See Delete a newly created EUCC.

Restore a deleted DT¶

Amend a DT¶

A DT in the Production state can be revised where certain changes can be made. Any end user can amend a DT that is in the Production state. He/she does not have to be its owner. To do that:

Find a DT in a non-working branch.
Open detail page of a DT in the Production state.
Click the “Amend” button at the top-right corner of the page. The DT goes into the WIP state; and its revision number increases by 1.
Only the following fields in the DT detail pane on the right may be updated.
1. Definition Source. Specify the source of the definition. This is typically a URI but the field accepts a free form text. Definition Source is optional.
2. Definition. Specify the description of the BCCP. Definition is optional but a warning is given if none is specified.
3. Content Component Definition. Specify the definition of the DT’s Content Component value. This is typically a free form text. Content Component Definition is optional.

Click the “Update” button at the top right to save changes.
The end user may want to perform these other actions on the DT:

Cancel a DT amendment¶

Change DT states¶

See Change EUCC states.

Transfer ownership of a DT¶

View history of changes to a DT¶

See View Change History of an EUCC.

Common End User CC Management Functions¶

The user guide in this section commonly applies to end user BCCP, ASCCP, and ACC.

Delete a newly created EUCC¶

Similar to Delete a newly created CC, an end user can put an EUCC into the deleted state. The EUCC has to have revision #1. This signifies that the owner of the deleted CC does not want to use it anymore. It suggests that if the EUCC is used by another end user, he/she should consider using another component. It is recommended that the owner documents the reason for deletion in the Definition field before deleting. Other end users (or the owner himself) can however restore the EUCC – See Restore a deleted EUCC. To delete a EUCC:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more EUCCs to delete. See Search and Browse CC Library for help in locating an EUCC. Individual EUCC management sections also contain additional tips to search for EUCCs.
There are two ways to delete a EUCC.
1. Delete one or more EUCCs simultaneously.
  1. Check the checkbox in front of one or more EUCCs that are in the WIP state, have revision 1, and are owned by the current end user.
  2. A trash icon is displayed at the top-right corner of the page.
  3. Click the trash icon.
2. Delete an EUCC individually.
  1. Click on the DEN of the EUCC to open its detail page. The EUCC must be in the WIP state, has revision 1, and is owned by the current end user.
  2. Click the “Delete” button at the top-right corner.
Confirm (or cancel) the deletion on the pop-up dialog.

Restore a deleted EUCC¶

Once an EUCC is deleted, the ownership is delinquent from the current owner. Any other end users can restore the EUCC to the WIP state and take the ownership. To restore an EUCC:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more EUCCs to restore from deletion. See Search and Browse CC Library for help in locating a EUCC. There are two ways to restore an EUCC.
1. Restore one or more EUCCs simultaneously.
  1. Check the checkbox in front of the EUCCs that are in the Deleted state.
  2. A trash can with an arrow icon inside is displayed at the top-right corner of the page.
  3. Click the icon.
2. Restore an EUCC individually.
  1. Click on the DEN of a deleted EUCC to open its detail page.
  2. Click the “Restore” button at the top-right corner of the page.
Confirm (or cancel) the restoration on the pop-up dialog.

Cancel an EUCC amendment¶

The end user who is the owner of a EUCC being amended can cancel the amendment. In this case, all changes to the EUCC are discarded. EUCC detail and its owner are rollbacked to the pre-amendment state. To cancel an EUCC amendment:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find the EUCC to cancel its amendment. See Search and Browse CC Library for help in locating the desired EUCC. Individual EUCC management sections also contain additional tips to search for EUCCs.
Click on the DEN of the EUCC to open its detail page. The current user has to be the owner of the EUCC and the EUCC has to be the WIP state with revision number greater than 1.
Click the “Cancel” button at the top-right of the page.
Confirm (or cancel) the amendment cancellation on the pop-up dialog.

Change EUCC states¶

The section covers the toggling between WIP, QA, and Production EUCC states. For detailed meaning of these and other states, see EUCC States. The current user has to be the owner of the EUCC to toggle between these three states. To change the EUCC state:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more EUCCs to change the state. See Search and Browse CC Library for help in locating a EUCC. Individual EUCC management sections contain additional tips to search for EUCCs.
There are two ways to change state of a EUCC:
1. Change the state of one or more EUCCs simultaneously.
  1. Check the checkbox in front of one or more CCs that are in the same state and owned by the current end user.
  2. Arrow icons are displayed at the top-right corner of the page. Depending on the current state of the selected EUCC; left, right, or both arrow icons are displayed.
  3. Click the left arrow icon to retract the state or click the right arrow icon to advance the state.
2. Change the state of EUCC individually:
  1. Open the “Core Component detail” page by clicking the DEN of the EUCC in WIP or QA, that is owned the current end user.
  2. Depending on the current state of the EUCC, click either the “Move to QA”, “Move to Production”, or “Back to WIP” (from QA) button at the top-right corner of the page.
3. Confirm (or cancel) the state change in the pop-up dialog.

Transfer ownership of an EUCC¶

To let another end user, make changes to an EUCC, the current owner has to transfer the ownership of the EUCC to another end user. EUCC can be transferred only to another end user. To transfer ownership:

Go to the “Core Component” page by clicking the “View/Edit Core Component” menu item under the “Core Component” menu. Find one or more EUCCs to transfer ownership. See Search and Browse CC Library for help in locating a EUCC. Individual EUCC management sections contain additional tips to search for EUCCs.
There are two ways to transfer ownership of an EUCC:
1. Transfer ownership of one or more EUCCs simultaneously.
  1. Check the checkbox in front of one or more EUCCs that are owned by the current end user and are in the WIP state.
  2. The double-arrow icon is displayed at the top-right corner of the page.
  3. Click the double-arrow icon.
  4. A dialog is displayed to select an end user to transfer the ownership to. Use the filter on the top to find the desired end user and check the checkbox in front of it.
  5. Click the “Transfer” button.
2. Transfer ownership of a EUCC individually.
  1. On the “Core Component” page, when a EUCC is in the WIP state and is owned by the current end user, there is a double-arrow icon next to the username of the owner.
  2. Click the double-arrow icon.
  3. A dialog is displayed to select an end user. Use the filter on the top to find the desired end user and check the checkbox in front of it.
  4. Click the “Transfer” button.

View Change History of an EUCC¶