I believe a related table would be the kind of thing you're looking for.
Exactly how to set up the relationship would require a bit more elaboration on what you need. Can you give a more specific example of how you're using this?
Then you have to create a Global ID field and save that unique records ID inside and then build a relationship based on that new Global ID field to your related table. After this you can use that relationship to show that record from the table no matter what record your are on in the table. If you want to have the same thing in other tables you just do same thing again.
It's already a relational table. I have a number of patents, each with title, authors, filing date etc. I want to have a summary table/view that lists them all on a timeline of sorts, and I want to give each a dropdown menu that lists these basic parameters. One option is to manually re-write all these data in a text field, but I'd prefer to somehow link each parameter back to it's original instance, so that if it's edited in it's original instance, it's updated in the summary table. Maybe a single-line portal would do the trick?