Some entities will need to display metadata from other entities #10
Description
Ever entity instance (with a UUID) in IDS can have its own metadata associated with it, but sometime when you are looking at an entity, you want to see metadata from other related entities. This is how biologists are used to seeing metadata, because they normally only put metadata on data objects, not on processes.
Example:
Someone creates a project and uploads a BAM file. Because we know that a BAM file is output of an assembly process, we ask them to supply metadata about the BAM file, but also some information about that process (for which we have created an identifier without them requesting it). Later, when they come back to view the BAM file, they see both the metadata they supplied about it and the metadata they supplied about the process.
Suppose later, they decide they want to view the assembly process in IDS. From that window, because we know assembly takes fastq files as input, we can ask if they want to supply information about the input files. They are directed to a create data page, where they input the locations of the fastq files (e.g., SRA) and have the option to enter metadata about those files. When they go back to view the BAM file, they will see the metadata about the BAM file, and metadata about the assembly process, including some indication that there are also registered fastq files that were used in the assembly. However, to actually see which files were used in the assembly, they would have to go to the assembly process page.