06-21-2023 Team questions

Questions to discuss

#

Question

Thoughts, answers

1

SN: "Fund code" and "Purchase order line number" fields are blank in "Error" file 

SN: Fund code can be added to 'Error' file by modifying FYRO script, for providing POL number need UI effort to query POL numbers by POL ids before generating csv file

Related story: MODFIN-260 - Getting issue details... STATUS


2

SN: Env created by automation pipeline is ready, are we okay to redeploy it to 

consortia rancher namespace : https://folio-dev-consortia-mobius.ci.folio.org/

Now it deployed to: https://folio-dev-metadata-consortium.ci.folio.org/

(Consortium mode) and https://folio-dev-metadata-diku.ci.folio.org/ 

(Standalone mode)

SN: We can use job like this: https://jenkins-aws.indexdata.com/job/Rancher/job/folioNamespaceTools/job/createNamespaceFromBranch/324/

to create consortia env from stratch with empty DB and updated versions of modules when needed. Fresh Env with 3 tenants in consortium: consortium, university, college

and 1 standalone diku tenant will be created in 30 mins.  

DB: It is okay to redeploy today/tomorrow

3

SN: Do we need to enable reference/sample data on all tenants in the consortium,

now it is enabled on all tenants in automation pipeline.

If we enable we don't touch source for reference/sample data, remain source

as it was before?

Discussion was started in this page: 06-06-2023 Consortia questions

DB: for now it is okay, enable only reference data and disable sample data

OK: we need to enable in all consortium tenants reference data and turn of sample data


MS: For Not Consortia setups we can skip displaying source field for newly added configs, 

DB: It makes sence to not show source for not consortia setups, if source is null for Consortia setup - we will show 'Local'

4

SN: Revisit what fields shadow user should store. Link to source code

Just for understanding what fields shadow user stores now