Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
metamod:open_questions28 [2010-11-11 16:05:22] oysteint |
metamod:open_questions28 [2022-05-31 09:29:32] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Open questions ===== | ===== Open questions ===== | ||
| + | * [[better_config|Configuration issues]] | ||
| - | * How is it decided which metadata is displayed for the level 2 datasets in the search result. In the current implementation this varies between different datasets. | ||
| - | * The metadata should be displayed in its incoming format. We might wish at a later stage to enable a view of metadata in a specific format, i.e. xmlAsISO19115 in addition to its original format. This is currently possible in oai-pmh-streams. | ||
| - | * The top-level metadata is created from the latest file submissions. The metadata on the 2nd level may differ from the top-level metadata. The current PHP script checks, for all metadata elements, if all files have the same metadata value. If so (and the value is displayed on the top level), the value is not displayed on the second level. Values that varies between files are displayed. Values that are empy for all files are not displayed. The configurable limit on number of columns (SEARCH_APP_MAX_COLUMNS) is honored. If this limits what metadata are displayed, I think it is somewhat arbitrary which matadata are dropped. | ||
| - | * Should SEARCH_APP_SHOW_COLUMNS be honored at level 2? That is if a column on level 2 is not shown on level 1 and has different data, should it then be displayed if the column is not found in SEARCH_APP_SHOW_COLUMNS | ||
| - | |||
| ===== Answered questions ===== | ===== Answered questions ===== | ||
| Line 16: | Line 12: | ||
| * The limit should only be evaluated before creating the archive. | * The limit should only be evaluated before creating the archive. | ||
| * As alternative, | * As alternative, | ||
| + | |||
| + | * How is it decided which metadata is displayed for the level 2 datasets in the search result. In the current implementation this varies between different datasets. | ||
| + | * The metadata should be displayed in its incoming format. We might wish at a later stage to enable a view of metadata in a specific format, i.e. xmlAsISO19115 in addition to its original format. This is currently possible in oai-pmh-streams. | ||
| + | * The top-level metadata is created from the latest file submissions. The metadata on the 2nd level may differ from the top-level metadata. The current PHP script checks, for all metadata elements, if all files have the same metadata value. If so (and the value is displayed on the top level), the value is not displayed on the second level. Values that varies between files are displayed. Values that are empy for all files are not displayed. The configurable limit on number of columns (SEARCH_APP_MAX_COLUMNS) is honored. If this limits what metadata are displayed, I think it is somewhat arbitrary which matadata are dropped. | ||
| + | * Should SEARCH_APP_SHOW_COLUMNS be honored at level 2? That is if a column on level 2 is not shown on level 1 and has different data, should it then be displayed if the column is not found in SEARCH_APP_SHOW_COLUMNS | ||
| + | * It is okay to honor it. If differences only exist in invisible columns, it might be nice to show the otherwise invisible, too. --- // | ||