Other Identifier not appearing in the Workbench

[tlammer]

Pointed out by a user in a webinar. The Other Identifier table is not offered as an option under Collection Object, so they can't upload their other identifiers while uploading their specimen data.

[maxpatiiuk]

The other identifiers table is denoted as a system table in the data model.

All system tables are hidden from the mapper. Though, there is no particular reason for doing that, so we can either provide a way to unhide system tables, or make an exception for the Other Identifier table

[maxpatiiuk]

If I enable otherIdentifier in the mapper, I get a back-end exception during dataset upload:

specify7-specify7-worker-1  | Traceback (most recent call last):
specify7-specify7-worker-1  |   File "/opt/specify7/ve/lib/python3.6/site-packages/celery/app/trace.py", line 405, in trace_task
specify7-specify7-worker-1  |     R = retval = fun(*args, **kwargs)
specify7-specify7-worker-1  |   File "/opt/specify7/ve/lib/python3.6/site-packages/celery/app/trace.py", line 697, in __protected_call__
specify7-specify7-worker-1  |     return self.run(*args, **kwargs)
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/tasks.py", line 41, in upload
specify7-specify7-worker-1  |     do_upload_dataset(collection, uploading_agent_id, ds, no_commit, allow_partial, progress)
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/upload.py", line 112, in do_upload_dataset
specify7-specify7-worker-1  |     base_table, upload_plan = get_ds_upload_plan(collection, ds)
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/upload.py", line 159, in get_ds_upload_plan
specify7-specify7-worker-1  |     return base_table, plan.apply_scoping(collection)
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/upload_table.py", line 29, in apply_scoping
specify7-specify7-worker-1  |     return apply_scoping(self, collection)
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/scoping.py", line 94, in apply_scoping_to_uploadtable
specify7-specify7-worker-1  |     toMany={f: [set_order_number(i, r.apply_scoping(collection)) for i, r in enumerate(rs)] for f, rs in ut.toMany.items()},
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/scoping.py", line 94, in <dictcomp>
specify7-specify7-worker-1  |     toMany={f: [set_order_number(i, r.apply_scoping(collection)) for i, r in enumerate(rs)] for f, rs in ut.toMany.items()},
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/scoping.py", line 94, in <listcomp>
specify7-specify7-worker-1  |     toMany={f: [set_order_number(i, r.apply_scoping(collection)) for i, r in enumerate(rs)] for f, rs in ut.toMany.items()},
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/tomany.py", line 20, in apply_scoping
specify7-specify7-worker-1  |     return apply_scoping(self, collection)
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/scoping.py", line 146, in apply_scoping_to_tomanyrecord
specify7-specify7-worker-1  |     scopingAttrs=scoping_relationships(collection, table),
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/workbench/upload/scoping.py", line 43, in scoping_relationships
specify7-specify7-worker-1  |     table.get_relationship('institution')
specify7-specify7-worker-1  |   File "/opt/specify7/specifyweb/specify/load_datamodel.py", line 108, in get_relationship
specify7-specify7-worker-1  |     assert isinstance(field, Relationship)
specify7-specify7-worker-1  | AssertionError

[benanhalt]

@maxpatiiuk I changed OtherIdentifier to not be a system table, but it still doesn't show up in the mapper. Did you have to change something else?

[maxpatiiuk]

I have just pushed the required wb mapper change in e7c43c9

[benanhalt]

Are you using some sort of cache here? After I removed the system status from the table, it still wasn't showing up. After applying e7c43c9 it did start to show up, but going back to production and putting the system status back, I can't get it not to show up.

[maxpatiiuk]

Yes, workbench mapper tables are cached.
That commit basically told the mapper to not throw out Other Identifier table and to wipe the workbench mapper tables cache

The cache is used not just in the mapper, but also in the workbench and by the leaflet map (on the locality form)

To clear the cache:

1. Open the specify 7 welcome page
2. Reload the page
3. Open DevTools
4. Open the "Console" tab in DevTools
5. Run this command: localStorage.clear()
6. Refresh the page
7. Close DevTools