We're updating the issue view to help you get more done. 

Expand importer splitter "parents" options for handling hierarchical numbering schemes


To improve import of hierarchies where the numbering scheme reflects the hierarchical structure (common when dealing with collection-level records), we need to add:

1. Normalization of numbers such that an abbreviated number in the data source is intelligently padded out to full length. Eg. If the numbering scheme for a folder-level collection record is 6 numbers (Ex. 2020., the last of which is auto-generated, but the data fewer numbers (Ex. 2020.5.3.3), this option will pad out the "missing" numbers with 1's. Thus 2020.5.3.3.% in the mapping becomes 2020. for import. (This sort of mismatched data is occurring in Riverside, for example). This option should require explicit activation in the mapping – by default is should be disabled.

2. A way to include the idno generated for an entry in the "parents" mapping in the mapping for its direct child. This will simplify import of cascading hierarchical identifiers where some of the identifier is inferred from context rather than directly mapped from source data. The value should be accessible via a placeholder tag (Eg. ^PARENT_IDNO)

3. A way to access the idno generated at any level of the "parents" mapping above the level of the mapping currently being evaluated (Eg. the identifiers generated for any parent of the currently processed parent entry). These should be numbered from one (where one is the highest level of the hierarchy) and exposed as placeholder tags (EG. ^LEVEL_1, ^LEVEL_2)

4. An option to prefix the imported idno values for a parent entry with a value only when the idno value is non-empty. This will allow us to prefix all entries of the parent hierarchy with a value will still skipping any empty levels.









Fix versions

Affects versions