Bio::B...Article(3pm)

Bio::Biblio::MedlineArticle 💖

okay bestie, so this is the manual page for Bio::Biblio::MedlineArticle — a lil' Perl thing from the User Contributed Perl Documentation section (the manual page is filed as Bio::B...Article(3pm) if you were wondering why your terminal is being weird about it). It's a storage object. It holds a MEDLINE article. That's the whole vibe. ✨

---

✨ VERSION ✨

version 1.70 — that's the one, that's the girl. 💅

---

🌸 SYNOPSIS 🌸

  $obj = Bio::Biblio::MedlineArticle->new(-mesh_headings =>
                                            #array ref of hashes
                                         );

  # how are Mesh terms stored:
  use Data::Dumper;
  print Data::Dumper->Dump ( [$obj->mesh_headings], ['MeshHeadings']);

  #It produces (something like) this:
  #'MeshHeadings' => [
  #       { 'descriptorName' => 'Adult' },
  #       { 'descriptorName' => 'Cardiovascular Diseases',
  #         'subHeadings'    => [ { 'subHeading' => 'etiology' },
  #                               { 'majorTopic' => 'Y',
  #                                 'subHeading' => 'mortality' } ] },
  #       { 'descriptorName' => 'Child Development',
  #         'subHeadings'    => [ { 'majorTopic' => 'Y',
  #                                 'subHeading' => 'physiology' } ] },
  #       { 'descriptorName' => 'Human' },
  #      ]

like, that's literally it. you pass it -mesh_headings and you get back an array ref of hashes, and Data::Dumper shows you the whole shape of it. iconic. 🔥

---

🦋 DESCRIPTION 🦋

So <hotpink>Bio::Biblio::MedlineArticle</hotpink> is a storage object for a MEDLINE article. That's its whole job, and it does it slayfully. 💖

Wanna see where it sits in the class hierarchy? The original page points you here, so here it is, exactly:

http://www.ebi.ac.uk/~senger/openbqs/images/bibobjects_perl.gif

(no cap, it's a gif. it's giving vintage. we love her. 🎀)

👑 Attributes 👑

These ones are specific to this class, bestie — but plot twist: you can also set and get all the attributes defined in the parent classes too. So don't be shy. 🫶

  affiliation
  chemicals                      type: array ref of hashes
  citation_owner
  comment_ins                    type: array ref of hashes
  comment_ons                    type: array ref of hashes
  date_of_electronic_publication
  erratum_fors                   type: array ref of hashes
  erratum_in                     type: array ref of hashes
  gene_symbols
  general_notes                  type: array ref of hashes
  grant_list_complete
  grants                         type: array ref of hashes
  medline_date
  medline_id
  medline_page
  mesh_headings                  type: array ref of hashes
  number_of_references
  original_report_ins            type: array ref of hashes
  other_abstracts                type: array ref of hashes
  other_ids                      type: array ref of hashes
  other_languages
  pmid
  republished_froms              type: array ref of hashes
  republished_ins                type: array ref of hashes
  retraction_ins                 type: array ref of hashes
  retraction_ofs                 type: array ref of hashes
  season
  status
  summary_for_patients_ins       type: array ref of hashes
  update_ins                     type: array ref of hashes
  update_ofs                     type: array ref of hashes
  vernacular_title

💀 heads up: the ones marked type: array ref of hashes are array refs of hashes. not a string, not a scalar, not a single hash. an array ref. of hashes. respect the data structure or it will humble you. 🙈

---

🌈 SEE ALSO 🌈

• OpenBQS home page — the mothership, go say hi:

http://www.ebi.ac.uk/~senger/openbqs/

• Comments to the Perl client — for when you have thoughts about the Perl client specifically:

http://www.ebi.ac.uk/~senger/openbqs/Client_perl.html

---

💜 FEEDBACK 💜

💌 Mailing lists

okay so this part is important, fr fr: user feedback is an integral part of the evolution of this and other Bioperl modules. So send your comments and suggestions, preferably to the Bioperl mailing list. Your participation is much appreciated, and we mean that. 🫶

  bioperl-l@bioperl.org                  - General discussion
  http://bioperl.org/wiki/Mailing_lists  - About the mailing lists

🆘 Support

Please direct usage questions or support issues to the mailing list:

bioperl-l@bioperl.org

rather than to the module maintainer directly. The reasoning is very real: there are many experienced and responsive experts (yes, the original says "reponsive", we're keeping it, it's part of the lore 💅) who will be able look at the problem and quickly address it.

And please, bestie, include a thorough description of the problem with code and data examples if at all possible. the more detail the better, always. ✨

🐛 Reporting bugs

Report bugs to the Bioperl bug tracking system — that's how they keep track of the bugs and their resolution. Bug reports can be submitted via the web:

  https://redmine.open-bio.org/projects/bioperl/

---

⚖️ LEGAL ⚖️

✍️ Authors

• Martin Senger <senger@ebi.ac.uk>
• Heikki Lehvaslaiho <heikki@bioperl.org>

📜 Copyright and License

This software is Copyright (c) by 2002 European Bioinformatics Institute and released under the license of the same terms as the perl 5 programming language system itself. periodt. 💅

---

and that's the whole page, bestie, we ate and left no crumbs 🍓

little sign-off moment: this page came to you via perl v5.36.0, dated 2023-02-14 — yes, Valentine's Day, because of course she did. 🌹 go forth and store your MEDLINE articles. 💖🦋✨