A possible requirement has been identified after discussions with Oli (probably on hold for now)
There is a need for users to use an ID when importing Vice Counties/Countries
This issue is just a note to myself (AVB) that there might be an easy solution to this. The Vice Counties and Countries are stored as custom lists in the configuration of the Plant Portal Plot Data Importer page, as well as associated warehouse module. We don't actually talk to the warehouse locations for reasons of speed, simplicity and flexibility.
It is possible that all I might need to do is extend the existing lists to include entries for the IDs as well as the names.
This would mean each Vice County would have two entries, an ID and a name.
The only drawback I can think of is the ID would get stored in the Vice County field on the sample, it is open as to whether that would be an issue, it does have the advantage that it represents the entry the user actually made, but the obvious disadvantage would be that it might affect functionality using this field.
I don't think there is any action to take right now, am just keeping these ideas here so they are not forgotten.
A possible requirement has been identified after discussions with Oli (probably on hold for now)
There is a need for users to use an ID when importing Vice Counties/Countries
This issue is just a note to myself (AVB) that there might be an easy solution to this. The Vice Counties and Countries are stored as custom lists in the configuration of the Plant Portal Plot Data Importer page, as well as associated warehouse module. We don't actually talk to the warehouse locations for reasons of speed, simplicity and flexibility. It is possible that all I might need to do is extend the existing lists to include entries for the IDs as well as the names. This would mean each Vice County would have two entries, an ID and a name. The only drawback I can think of is the ID would get stored in the Vice County field on the sample, it is open as to whether that would be an issue, it does have the advantage that it represents the entry the user actually made, but the obvious disadvantage would be that it might affect functionality using this field.
I don't think there is any action to take right now, am just keeping these ideas here so they are not forgotten.
Nested in #46