Details
-
New Feature Request
-
Resolution: Canceled
-
Major
-
None
-
MONARCH 1.0
-
None
-
NIF
-
Issues closed as MONARCH has transitioned from UCSD services
Description
during the last sneak peak release, we figured out that the zp mapping file used by the ingest pipeline was a static one from last august ('13), and that the one in the repository (which wasn't being used in disco, but was being used in monarch) had unstable identifiers.
i believe the unstable identifiers issue has been fixed, but we are using the very old static zp mappings. we need to make sure that for the next monarch release we use the proper zp mapping file in the monarch import chain (assuming it has stable identifiers).