Mark Jordan

Currently, the OaiToDc and (new in the issue-439 branch) OaiToMods metadata parsers' `applyMetadatamanipulators()` method acts on XML snippets. This is probably because the code was simply copied from CONTENTdm toolchains...

Create releases, and establish roadmap or similar plan for future releases

8

In #370, @MarcusBarnes wrote: > I suggest that we start creating tagged releases of the code base (and documentation), running sample data through before each release as a double check...

If the directory specified in `[FILE_GETTER] input_directory` is does not exist, running MIK results in a segmentation fault/core dump. Running `--checkconfig` prior to running MIK doesn't catch this, since it...

Review how we are logging things, particularly exceptions or errors

5

Coming out of #296, we should centralize logging, particularly problem or error logging. Currently exception logging bubbles up to mik, which has worked well for us so far, but this...

Fetcher manipulators and metadata manipulators implement an abstract method, `->manipulate()`, whereas filegetter manipulators implement a different abstract method, `->getMasterFilePaths()`. This anomalous method is implemented in only one subclass, https://github.com/MarcusBarnes/mik/blob/master/src/filegetters/CdmSingleFile.php#L154. In...

The CdmToMods metadata parser's `getCollectionFieldConfig()` method makes an HTTP request to `$wsUrl . 'dmGetCollectionFieldInfo/' . $alias . '/json'` for every MODS record it creates. This could be cached, reducing the...

All metadataparser subclasses (MODS metadata parsers, Templated parser, the dc/OaiToDc parser, and the CsvToJson parser) all implement the `->metadata()` method in the same way. In the interests of a clean...

Add a filegetter for CSV toolchains that fetches a file from a URL

2

If the CSV input file has a field that contains a URL to a PDF, image, etc., we should be able to write a FileGetter that fetches the specified file.

Move XML utility functions from child classes into Mods.php

1

getChildNodesFromModsXMLString(), determineRepeatedWrapperChildElements(), consolidateWrapperElements(), oneParentWrapperElement(), and possibly applyMetadatamanipulators() are duplicated within CdmToMods.php and the new CsvToMods.php metadata parser. Is there any reason these functions can't live within the parent Mods.php class?

Should CONTENTdm and CSV toolchains generate only MODS.xml?

2

MIK was designed to write out either MODS or DC datastreams. For OAI-PMH toolchains, this makes sense since they will commonly harvest DC from the remote repository. However, is it...