Support for handling branch aliases
As a result of the need to keep automatically-generated branch names unique, branch names end up being large. To make interactive use of art/ROOT data files more convenient, we want to support branch aliases.The person running the program is the best to control what the branch aliases are. Issues to decide upon include:
- Where does this happen?
- How do aliases get transferred from input to output file?
- What happens when there is a collision?
- Do we handle collisions between the input and the current job differently from collisions within the current job?
Having the configuration of the branch alias specified in the output module makes it easy to deal with providing an alias for a product that came from an input file.