Frequently asked questions
This chapter contains the most frequently asked questions about managing the dictionaries using the Console self-service options:
- What are the prerequisites to load a dictionary?
- What are the mandatory files required to be zipped for a successful load?
- Are there any size restrictions for the dictionary files?
- Can I upload ZIP files from a remote or shared location?
- Why are the files zipped?
- Can I reuse the dictionary files?
- What is the MDB file?
- Does each dictionary type need a separate MDB file?
- From where can I get the MDB files for each dictionary?
- Do I need to upload the MDB file every load?
- When do I need to upgrade the MDB file?
- How do I know if my load is successful?
- What do I do if the dictionary loading process hangs?
- How can I load a dictionary in a multi-tenant environment?
- Can I work on cases or do other activities in Argus when loading a dictionary?
- Can I upload the same dictionary twice?
- Where is the dictionary files content stored?
- In which tablespace is the dictionary schema created? Can it be changed?
- How do I select the latest loaded dictionary for case coding?
- Is there a required downtime for MedDRA recode?
- What are the prerequisites for MedDRA recode?
- Why is the Update dictionary version for coded terms where existing hierarchy is still current field disabled when View Only is selected?
- How do I know if the recode is successfully completed?
- Can older recode logs be downloaded in self-service?
Parent topic: Manage dictionaries