Page History

...

Be aware that some metadata from the source might not display in the form, but might be saved in the object's MODS datastream regardless. The transforms transform from source the sources to MODS XML are defined by each populator/importer module, but the metadata form that displays can be configured by an Islandora administrator. If the form is missing fields for certain MODS elements, such as within <mods:relatedItem type="host">, that information may not show up in the form that the user sees, but will still be saved in MODS. Populator modules can be used to create objects of any content type, and this may happen if creating an object with a form that was not designed for citations.

Image RemovedImage Added

To use an Importer, log in, and browse to a Collection. Click the "Manage" tab, then the "Collection" sub-tab, then click "+ Batch Import Objects". You will get a drop down menu with an option to use the "DOI Importer" and any other importers that are enabled. Upload a file or list of DOIs, and click "Import" to automatically import the batch of objects. This uses the Islandora Batch interface behind the scenes, and you will be redirected to a "queue" if the ingest was successful. See How to Batch Ingest Files for more information about ingest queues. 

The importers bundled with Scholar will only create Citation content model objects. If your collection policy is set up so that the collection can hold Citation Content Model objects, then the import will create these objects, and will create them in the namespace configured for Citation objects in the collection.  If your collection policy is not set up to hold Citation Content Model objects, then the import will create objects in the ir: namespace. If namespace restrictions are enabled, these objects might not show up as expected.

Image Modified

DOI Importer/Populator - special configuration

...