PICA-Record 0.53
Kwalitee Issues
- meta_yml_conforms_to_known_spec
-
Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.
Error: License '<undef>' is invalid (license) [Validation: 1.3];Missing mandatory field, 'license' (license) [Validation: 1.3]
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: PICA-Record-0.53/lib/PICA/Field.pm -- Around line 315: Non-ASCII character seen before =encoding in ''@Traité'. Assuming UTF-8 PICA-Record-0.53/lib/PICA/Record.pm -- Around line 42: Non-ASCII character seen before =encoding in 'für'. Assuming UTF-8
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: PICA::Field, PICA::Parser, PICA::PlainParser, PICA::Record, PICA::SQLiteStore, PICA::SRUSearchParser, PICA::Source, PICA::Store, PICA::Writer, PICA::XMLParser
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.1,0.20,0.45,0.48,0.49,0.50,0.51,0.52,0.53
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
Name | Abstract | Version | View |
---|---|---|---|
PICA::Field | Perl extension for handling PICA+ fields | 0.51 | metacpan |
PICA::Parser | Parse PICA+ data | 0.49 | metacpan |
PICA::PlainParser | Parse normalized PICA+ | 0.50 | metacpan |
PICA::Record | Perl extension for handling PICA+ records | 0.53 | metacpan |
PICA::SOAPClient | L<PICA::Store> via SOAP access (aka 'webcat') | 0.45 | metacpan |
PICA::SOAPServer | provide a SOAP interface to a L<PICA::Store> | 0.1 | metacpan |
PICA::SQLiteStore | Store L<PICA::Record>s in a SQLite database with versioning | 0.20 | metacpan |
PICA::SRUSearchParser | Parse a SRU response in XML and extract PICA+ records. | 0.48 | metacpan |
PICA::Source | Data source that can be queried for PICA+ records | 0.53 | metacpan |
PICA::Store | CRUD interface to a L<PICA::Record> storage | 0.48 | metacpan |
PICA::Writer | Write and count PICA+ records and fields | 0.52 | metacpan |
PICA::XMLParser | Parse PICA+ XML | 0.51 | metacpan |