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

📦 version 1.70, in debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

💖 Bio::B...:Patent — the manual, but make it cute 💖

okay bestie, gather round, because today we're talking about Bio::B...:Patent(3pm), a little Perl module from the User Contributed Perl Documentation collection that is literally the main character of patent storage objects. yes, patents. the fancy legal ones. we're doing this. 💅

✨ NAME ✨

Bio::B...:Patent — it's a representation of a patent, periodt. 👑

🌸 VERSION 🌸

version 1.70 — that's the one, no cap. 🎀

🦋 SYNOPSIS 🦋

okay so here's how you summon one, two ways, pick your fighter:

$obj = Bio::Biblio::Patent->new(-doc_number => '1-2-3-4-5');

#--- OR ---

$obj = Bio::Biblio::Patent->new();
$obj->doc_number ('1-2-3-4-5');

like, you can pass the doc number in at construction time (iconic, efficient, we love her) OR you can make a blank one and set doc_number after the fact (also valid, no judgement, different vibe). ✨

💜 DESCRIPTION 💜

so basically it's a storage object for a patent. that's the whole thing. she holds patent info and she holds it well. 🌈

if you wanna see where she sits in the class hierarchy (her little family tree, her lineage, her ancestry dot gif), go look here:

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

🫶 Attributes 🫶

these are the attributes that are specific to this class — but heads up, you can also set and get all the attributes defined in the parent classes too, so don't feel limited bestie, the whole inheritance tree is yours: 💖

doc_number
doc_office
doc_type
applicants       type: array ref of Bio::Biblio::Providers

quick notes, because details matter:

  • doc_number — the number. of the doc. slay.
  • doc_office — the office that issued it.
  • doc_type — what kind of patent we're talking about.
  • applicants — this one is a type: array ref of Bio::Biblio::Providers, so it's a whole list of provider objects, not just one. she's an array ref, she contains multitudes. 💅

🔥 SEE ALSO 🔥

💌 FEEDBACK 💌

📬 Mailing lists 📬

user feedback is an integral part of the evolution of this and other Bioperl modules — like, the module grows because of you, that's the whole thing. 🥹 send your comments and suggestions, preferably to the Bioperl mailing list. your participation is much appreciated, fr fr.

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. why? because many experienced and responsive experts will be able to look at the problem and quickly address it. (yes, the original says "reponsive" — we're keeping it, that's canon, don't @ me. 😭)

and please include a thorough description of the problem with code and data examples if at all possible. the more detail the better, give them the whole lore. 🧚

🐛 Reporting bugs 🐛

report bugs to the Bioperl bug tracking system so they can keep track of the bugs and their resolution. bug reports can be submitted via the web:

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

✍️ Authors ✍️

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

legends, both of them. 👑

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.

okay that's the whole page, nothing skipped, nothing dropped, every flag and every line accounted for. you're welcome. 💖

and that's a wrap on perl v5.36.0, dated 2023-02-14, from the Bio::B...:Patent(3pm) manual page — happy patenting bestie, go be the main character of your own bibliography. 🎀🦋✨💜

📦 where this page comes from