I made fairly minimal change to the original code, to help the OP see how close they were to a solution. My idea of optimum would almost certainly be different and others would have other very good ideas - as you have. Details of the results aside, what you have written is quite appealing: I find it easier to read and understand than the original.

The code you wrote is not quite the same: for example you don't display the information following LOCUS, of which there is no example in the sample data provided, and you don't remove the quotes from the gene and transcript_id values.

The input data looks like an excerpt from a GeneBank flat file record. These files are quite complex and rather than writing my own software I would probably turn to BioPerl for modules to read these files.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.