After #54 actions won't be failing on failed data downloads and re-running actions to fetch missing data will be possible. This may result in generation of a couple of metadata/sequence artifacts that potentially contain data that should be stored in a single artifact.
As it is possible already to merge multiple sequence artifacts a similar action for metadata would be helpful - this PR introduces an action to merge multiple SRA metadata artifacts into a single table. For now, this is a simple outer concat: everything is retained (rows + columns) and duplicated rows are filtered out.
If anyone has ideas on expanding this action, give me a shout!
After #54 actions won't be failing on failed data downloads and re-running actions to fetch missing data will be possible. This may result in generation of a couple of metadata/sequence artifacts that potentially contain data that should be stored in a single artifact.
As it is possible already to merge multiple sequence artifacts a similar action for metadata would be helpful - this PR introduces an action to merge multiple SRA metadata artifacts into a single table. For now, this is a simple outer concat: everything is retained (rows + columns) and duplicated rows are filtered out.
If anyone has ideas on expanding this action, give me a shout!