Postgres loader does not allow different module identifiers (e.g., US1000124)

[boxydog]

In the README it says

Note that the scripted installation will now support loading other Editions. The script asks for a module identifier, which is INT by default, for the international edition. Loading the US Edition, for example, would work as follows: Enter module string used in filenames [INT]: US1000124

However, in the loader script it just uses "INT" without asking.

[siamchen]

You may need to change the release variable in the load-postgresql.sql file from INT_20180131 to US1000124. Most of the configurable information are in that file.

[boxydog]

Thanks for your help.

I actually just added a MODULE_STRING variable in load_release-postgresql.sh locally:

# MODULE_STRING=INT
MODULE_STRING=US1000124

addLoadScript sct2_Concept_TYPE_${MODULE_STRING}_DATE.txt concept
addLoadScript sct2_Description_TYPE-en_${MODULE_STRING}_DATE.txt description
addLoadScript sct2_StatedRelationship_TYPE_${MODULE_STRING}_DATE.txt stated_relationship
addLoadScript sct2_Relationship_TYPE_${MODULE_STRING}_DATE.txt relationship
addLoadScript sct2_TextDefinition_TYPE-en_${MODULE_STRING}_DATE.txt textdefinition
addLoadScript der2_cRefset_AttributeValueTYPE_${MODULE_STRING}_DATE.txt attributevaluerefset
addLoadScript der2_cRefset_LanguageTYPE-en_${MODULE_STRING}_DATE.txt langrefset
addLoadScript der2_cRefset_AssociationTYPE_${MODULE_STRING}_DATE.txt associationrefset

Worked for me.

I could submit a patch with that change (a MODULE_STRING variable, set to INT by default) if that would be helpful.

If the recommended path is hand-editing the script, I'd suggest changing the README.