As a user of the SITIPE plugin I want to import the IID file from the SQL database and add it to the XMLDocument
Requirements
when the user selected the bay template (VS1052) and the private sections have been written (VS1052) we need to add the IID file
first get the binary code of the IID file like so
get the accessId of the IED from ..._BTcomponents
get data binary from SELECT data FROM [databasename].[dbo].[frameworkIDImported] WHERE componentAccessId="..."
convert to XML string (SIEMENS itself is using this )
add the IID to the project
there is a plugin that is doing that BUT! the functions are not exported and they should not as we want to avoid direct dependency of plugins
either copy over the functionality or
create a PR to oscd-scl and re-use via npm
Open questions
do we want to reuse the ImportIED function in OpenSCD?
yes: how to reuse the import IED function of the ImportIED plugin?
take time to push on oscd-scl (could be an additional effort of 2 weeks)
copy over the function to the SITIPE plugin
DO NOT export from the ImportIED plugin!!
no: we need a extra story to do that in the backend with extra tests (ca. 2 weeks as well)
what library do we want to use to make binary to XML string?
DataBase dependencies
frameworkID: this is a variable given once per user e.g. Alliander. I this story is is given as cf3 and is needed to query the proper as it is part of the table name like so SELECT ... FROM [databasename].[dbo].[frameworkID]. ....
version: SITIPE is all around version control. This means that you can have multiple versions of everything in the data base. In this story the version is given as 1.00 . You can find the different version within SELECT version FROM [databasename].[dbo].[frameworkID_SYSTEM_VERSION_LIST]
As a user of the SITIPE plugin I want to import the IID file from the SQL database and add it to the XMLDocument
Requirements
Open questions
DataBase dependencies
frameworkID: this is a variable given once per user e.g. Alliander. I this story is is given as cf3 and is needed to query the proper as it is part of the table name like so SELECT ... FROM [databasename].[dbo].[frameworkID]. ....
version: SITIPE is all around version control. This means that you can have multiple versions of everything in the data base. In this story the version is given as 1.00 . You can find the different version within SELECT version FROM [databasename].[dbo].[frameworkID_SYSTEM_VERSION_LIST]