Page History

...

• Standard column headers come from LexEVS view.
• Need to consider “extended” columns that may not apply to all map sets (e.g. MAP_RANK, or other MRMAP fields like MAPPRIORITY, etc)

• Individual mapping view – link source and target codes to the concept pages for those things – may not need this
• “Mappings” tab on concept view – render all mappings “to” or “from” that concept

• need to determine which map sets to search in
• retrieve this info only when user actually clicks on this tab

• Make good decisions about when clicking should open a new window vs. reload in the same page.
• Support a “view all mappings” function for simple browsing of small sets (without requiring search).
• Handling expression-based mappings (may need to parse – can do based on grammar or “style”).
• Consider when a new page should open and when content should be reloaded in the current tab/browser window.

...