You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As currently implemented, metadata import for the supported formats (DC, DDI...) is hard-coded in the application. We should consider changing it to something similar to how the exports are implemented (as Exporter classes that ExportService loads dynamically). This would make it easier to add support for more formats (and, potentially, for harvesting from more sources).
If we wanted to be really fancy, we could add support for loading these as real dynamic plugins, that could be dropped in place, without needing to add the code to the application project).
The text was updated successfully, but these errors were encountered:
mreekie
added
NIH OTA: 1.4.1
4 | 1.4.1 | Resolve OAI-PMH harvesting issues | 5 prdOwnThis is an item synched from the product ...
and removed
NIH OTA: 1.4.1
4 | 1.4.1 | Resolve OAI-PMH harvesting issues | 5 prdOwnThis is an item synched from the product ...
labels
Oct 25, 2022
mreekie
removed
the
NIH OTA: 1.4.1
4 | 1.4.1 | Resolve OAI-PMH harvesting issues | 5 prdOwnThis is an item synched from the product ...
label
Nov 2, 2022
As currently implemented, metadata import for the supported formats (DC, DDI...) is hard-coded in the application. We should consider changing it to something similar to how the exports are implemented (as
Exporter
classes thatExportService
loads dynamically). This would make it easier to add support for more formats (and, potentially, for harvesting from more sources).If we wanted to be really fancy, we could add support for loading these as real dynamic plugins, that could be dropped in place, without needing to add the code to the application project).
The text was updated successfully, but these errors were encountered: