Skip to content

Bitstream audit: altered filenames during migration #15

@jefferya

Description

@jefferya

During SAF package creation, if a bitstream filename was duplicated then an identifier was added (e.g., a.pdf ==> `a_uuid.pdf`` thus a direct comparison from ERA to Scholaris on the filename fails here:

"name": {
"columns": {"jupiter": "filename", "dspace": "bitstream.name"},
"comparison_function": string_compare_ignore_whitespace,
},

Idea to fix

  • quick: create a new comparison function that removes the added part
  • longer: use syntax like the "special_type_compare" to pass multiple columns into the comparison and try to match the addition to the filename string:
    def special_type_compare(row, key, value):

    The later exception to the cleaner rules grew like one-time code sometimes does.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions