For an upcoming batchload, each Item will have multiple Bitstreams, and to distinguish the Bitstreams, we'd like to associate the bitstream-level metadata of bitstream description.
Currently to do this through this tool, you can use a delimiter such as double-underscore, followed by the key, followed by the value.
The import tool additionally allows the following as extra parameters for a file.
Maybe that convention works if you've got a lot of homogenous content to ingest, but if each Bitstream might have a different description/caption, then the only way to support that is to make lots of columns:
So, how do we mash it up and turn this up to 11 you ask? Since a user might still want to pass a "global" parameter by editing the filename column header, so that the file itself will inherit those values.
For an upcoming batchload, each Item will have multiple Bitstreams, and to distinguish the Bitstreams, we'd like to associate the bitstream-level metadata of bitstream description.
Currently to do this through this tool, you can use a delimiter such as double-underscore, followed by the key, followed by the value.
The import tool additionally allows the following as extra parameters for a file.
For this example, we'd have to edit the column header to make it say:
Maybe that convention works if you've got a lot of homogenous content to ingest, but if each Bitstream might have a different description/caption, then the only way to support that is to make lots of columns:
So, what if we let the user put parameters directly into the file's name itself. filename my-poster.pdf__description:Presentation Poster
If you have multiple Bitstreams for the Item, then use the repeated entry delimeter of double-pipe.
So, how do we mash it up and turn this up to 11 you ask? Since a user might still want to pass a "global" parameter by editing the filename column header, so that the file itself will inherit those values.