Categories
Bez kategorii

Join Publishers

We cordially invite the publishers of scientific journals and books to make their publications available in the Library of Science.

Our goal is to increase the visibility and availability of Polish scientific publications, which for publishers implies reaching new communities of readers and authors. The cooperation with us is free of charge and non-exclusive. We may host current as well as archival issues.

The Library of Science hosts over 1500 Polish scientific journals that yield a few hundred thousand articles altogether. We are well visible on the internet, our content is indexed by search engines and it is also easily available through a public API. For many users, ICM UW services, including the Library of Science, are a default starting place for searching for scientific content.

The platform allows to browse full-text resources originating from five thematic databases:

  • AGRO (journals on natural and agricultural sciences)
  • BazTech (journals in engineering and technology and exact sciences)
  • CEJSH (journals in humanities, social sciences, theology and arts)
  • DML-PL (journals in mathematics)
  • PSJD (journals in medical and health sciences).

The publications are made available in the Library of Science on the basis of contracts concluded by publishers with ICM UW. The contracts are mutually free of charge and non-exclusive, and as such they do not restrict publishers in their possibilities to make their content available elsewhere.

The representatives of publishers cooperating with ICM are given user accounts allowing them to access their publisher’s profile. Registered users also have access to the application allowing them to manage their publisher’s resources on the platform. It allows for automatization of metadata input (e.g., by importing from systems such as OJS) and simplifies work reporting (e.g., by downloading statistics and reports).

For our current and incoming users we offer free of charge training in technical, operational and legal issues of Open Access. We offer technical support in the input and editing of data and legal support in relation to the implementation of free licenses.

For inquiries about commencing cooperation please contact: lp.ik1652725303uanak1652725303etoil1652725303bib@y1652725303cwady1652725303w1652725303

Categories
Bez kategorii

Contact

The Library of Science is a service run by the Open Science Platform (PON) team operating as part of the Interdisciplinary Centre for Mathematical and Computational Modelling of the University of Warsaw.

Main page of the ICM UW: https://icm.edu.pl

Open Science Platform page: https://pon.edu.pl

Contact with the Open Science Platform team: lp.ud1652725303e.mci1652725303@nop1652725303

Contact in matters related to the use of the Library of Science: lp.ik1652725303uanak1652725303etoil1652725303bib@k1652725303sedpl1652725303eh1652725303

Contact for cooperation for publishers of scientific publications: lp.ik1652725303uanak1652725303etoil1652725303bib@y1652725303cwady1652725303w1652725303

Public Information Bulletin of the University of Warsaw:
https://uwedupl.bip.gov.pl/

Categories
Bez kategorii

Privacy and cookies policy

Cookies

We use cookies to run the Library of Science (more about cookies at: https://en.wikipedia.org/wiki/HTTP_cookie/). Using the Library of Science implies that they will be stored on your device. At any moment you may change the settings of your browser.

Types of cookies used by the Library of Science:

  • performance – collecting information about the way visitors use the service;
  • operational – necessary to service the registered users.

Third-party services that may be linked to in the Library of Science may use other cookies than indicated above. These services follow privacy policies specified by their administrators. Please make yourself acquainted with such policies after navigating to these sites.

The Library of Science stores http requests addressed to our server. The resources are identified by URL addresses. WWW server log files contain the following information:

  • public IP address of the computer that sent the request,
  • number of bytes sent by the server,
  • information about user’s browser,
  • information about time when the data was sent from the server.

The information does not contain data pertaining to user identity, but when aggregated with other information may constitute personal data. Therefore, the data controller subjects them to full protection available under the law on personal data.

The log files are retained for an unspecified period of time as an auxiliary material for administering the Library of Science. Their contents are not revealed to anyone except persons authorised to administer the Library of Science. Log files are used to generate statistics to help in administering.

Personal data of registered users – excerpt from the Library of Science – Terms of Use

  1. The personal data controller for the Users’ data is the University of Warsaw with its registered seat at Krakowskie Przedmieście 26/28, 00-927 Warszawa. Users may contact the data controller in one of the manners provided at: https://www.uw.edu.pl/kontakt/.
  2. The data controller has appointed a Data Protection Officer (DPO) who supervises the correct processing of personal data at the University of Warsaw. Users may only approach the DPO with matters related to the processing of personal data by the University of Warsaw. Users may contact the DPO via e-mail, by sending a message to: lp.ud1652725303e.wu.1652725303mda@d1652725303oi1652725303.
  3. The Users’ personal data will be processed for the purposes of providing the Library of Science services.
  4. The following personal data of the Users is processed as part of operating the Library of Science:
    1. login
    2. name and surname;
    3. email address;
    4. password in encrypted format;
    5. IP address;
    6. user role.
  5. Personal data is processed pursuant to Article 6 section 1 letters b, c, e and f of the Regulation of the European Parliament and of the Council (EU) 2016/679 of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation; hereinafter referred to as GDPR). Data is processed for the time when the User has an account in the Library of Science and once it is removed – for the period of storing the data uploaded by the individual User into the Library of Science and for 5 years after their removal.
  6. Registered users, when using functions of the Library of Science related to uploading data, receive the following data of other Users: name, surname and login, while Users with administrative permissions also receive the email address.
  7. Personal data collected in the Library of Science may be transferred to third parties for the purposes required for the proper functioning of the Library of Science and only to the extent necessary. Data may also be made available to third parties in other cases specified by the law.
  8. A data subject has the right to (subject to the terms stipulated in the GDPR):
    1. obtain access to their data (Article 15 of the GDPR);
    2. rectify (correct) their data (Article 16 of the GDPR);
    3. delete their data (Article 17 of the GDPR);
    4. restrict the processing of their data (Article 18 of the GDPR);
    5. object to the processing of their data (Article 21 of the GDPR);
    6. withdraw their consent the processing of their data at any time (Article 7 of the GDPR);
    7. lodge a complaint with the President of the Personal Data Protection Office if they believe that the processing of their personal data violates the GDPR (Article 77 of the GDPR).
  9. Providing personal data by the User is necessary to register with the Library of Science. Refusal to provide data will result in the inability to use the resources of the Library of Science.
Categories
Bez kategorii

Library of Science – Terms of Use

§ 1. General provisions

  1. These Terms of Use govern the use of the electronic platform for scientific publications (“Library of Science”).
  2. The Library of Science is operated by the University of Warsaw – Interdisciplinary Centre for Mathematical and Computer Modelling (ICM) with its registered seat in Warsaw (00-927) at ul. Krakowskie Przedmieście 26/28, 00-927 Warszawa (“University”) via the Library of Science website (https://bibliotekanauki.pl).
  3. The purpose of the Library of Science is to make scientific papers and books („Scientific Publications”) available on the Internet.

§ 2. Rules for using the Library of Science

  1. The Library of Science service enables the following:
    1. storing Scientific Publications;
    2. making Scientific Publications publicly available;
    3. browsing Scientific Publications;
    4. downloading Scientific Publications.
  2. Browsing and downloading Scientific Publications is available in an open formula, free of charge to all those interested, subject to the terms of the applicable licenses.
  3. Users may use features available according to the current technical status of the Library of Science.
  4. Scientific Publications are stored and made publicly available under separate agreements concluded between the University and the publishers of these Scientific Publications, while using the related features requires registration in the Library’s electronic system.
  5. There are no special technical requirements for using the Library of Science, except for some of its specific features. Information about the current specific technical requirements is communicated on an ongoing basis in the Library of Science.

§ 3. Storing and making Scientific Publications publicly available

  1. A registered user may store and make Scientific Publications publicly available in the Library of Science.
  2. Users are forbidden to upload illegal content into the Library of Science, including, but not limited to storing and making available the following types of content in the Library of Science:
    1. contents to the dissemination of which the User does not hold a valid legal title;
    2. the dissemination of which breaches other third party rights, including their personal rights;
    3. the dissemination of which is contrary to other legal provisions than those resulting from sections 2.a and 2.b.
  3. By uploading metadata of Scientific Publications into the Library of Science, a User submits a statement that is in line with the contents of the Creative Commons 0 template, the full text of which is available at: https://creativecommons.org/publicdomain/zero/1.0/legalcode („CC0”). The scope of this statement only includes metadata but not the contents of the Scientific Publications.
  4. Files that contain the Scientific Publications may be made publicly available by the User for use by third parties under the applicable public domain provisions, fair use or other freedoms stipulated under the law, or under the provisions of a license selected by the User from the list available in the Library of Science.
  5. Metadata and full text versions of Scientific Publications uploaded by Users are subject to verification by administrators authorized by the University.
  6. Detailed matters related to storing and making Scientific Publications available in the Library of Science shall be stipulated in separate agreements between University and the publishers of these Scientific Publications.

§ 4. Complaints, queries and comments

  1. Complaints, queries and comments should be sent by registered mail to: Interdyscyplinarne Centrum Modelowania Matematycznego i Komputerowego, Uniwersytet Warszawski [Interdisciplinary Centre for Mathematical and Computer Modelling, University of Warsaw] ul. Tyniecka 15/17, 02-630 Warszawa or sent by electronic mail to lp.ik1652725303uanak1652725303etoil1652725303bib@k1652725303sedpl1652725303eh1652725303.
  2. The submission should provide sufficient details about the submitter, allowing for their identification, as well as the complaint, query or comment together with a short description of the issue.
  3. Submissions will be processed without unnecessary delay and submitters shall be notified of the results at the address indicated in their submission.

§ 5. Personal data and privacy policy

  1. The personal data controller for the Users’ data is the University of Warsaw with its registered seat at Krakowskie Przedmieście 26/28, 00-927 Warszawa. Users may contact the data controller in one of the manners provided at: https://www.uw.edu.pl/kontakt/.
  2. The data controller has appointed a Data Protection Officer (DPO) who supervises the correct processing of personal data at the University of Warsaw. Users may only approach the DPO with matters related to the processing of personal data by the University of Warsaw. Users may contact the DPO via e-mail, by sending a message to: lp.ud1652725303e.wu.1652725303mda@d1652725303oi1652725303.
  3. The Users’ personal data will be processed for the purposes of providing the Library of Science services.
  4. The following personal data of the Users is processed as part of operating the Library of Science:
    1. login
    2. name and surname;
    3. email address;
    4. password in encrypted format;
    5. IP address;
    6. user role.
  5. Personal data is processed pursuant to Article 6 section 1 letters b, c, e and f of the Regulation of the European Parliament and of the Council (EU) 2016/679 of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation; hereinafter referred to as GDPR). Data is processed for the time when the User has an account in the Library of Science and once it is removed – for the period of storing the data uploaded by the individual User into the Library of Science and for 5 years after their removal.
  6. Registered users, when using functions of the Library of Science related to uploading data, receive the following data of other Users: name, surname and login, while Users with administrative permissions also receive the email address.
  7. Personal data collected in the Library of Science may be transferred to third parties for the purposes required for the proper functioning of the Library of Science and only to the extent necessary. Data may also be made available to third parties in other cases specified by the law.
  8. A data subject has the right to (subject to the terms stipulated in the GDPR):
    1. obtain access to their data (Article 15 of the GDPR);
    2. rectify (correct) their data (Article 16 of the GDPR);
    3. delete their data (Article 17 of the GDPR);
    4. restrict the processing of their data (Article 18 of the GDPR);
    5. object to the processing of their data (Article 21 of the GDPR);
    6. withdraw their consent the processing of their data at any time (Article 7 of the GDPR);
    7. lodge a complaint with the President of the Personal Data Protection Office if they believe that the processing of their personal data violates the GDPR (Article 77 of the GDPR).
  9. Providing personal data by the User is necessary to register with the Library of Science. Refusal to provide data will result in the inability to use the resources of the Library of Science.

§ 6. Liability

  1. The University undertakes best efforts to enable using the Library of Science without material downtimes or other interruptions, making it compatible with the largest number of possible hardware and software setups available in the market.
  2. If an official authority submits a notification or if credible information is obtained about the illegal nature of Scientific Publications or related activities, University shall immediately disable access to the indicated Scientific Publications in the Library of Science.
  3. The University may refuse to store and make Scientific Publications publicly available and may also block access or remove the data that does not constitute a Scientific Publications under the Terms and Conditions from the Library of Science, as well as data not complying with these Terms and Conditions. The University verifies the validity of metadata and technical validity of files.
  4. The University may refuse to register or remove the account of a User who breaches the Terms and Conditions and does not remedy the breach upon a 14-day notice.

§ 7. Modification of the Terms and Conditions

  1. The University shall inform the User of modifications to these Terms and Conditions by electronic mail sent to the addresses registered with the User’s account.
  2. A User that does not consent to modifications of these Terms and Conditions may request removal of their User account. These Terms and Conditions cease to bind the User from the date of removal of their account.
  3. A User who received information on a modification of the Terms and Conditions and did not demand their account to be removed at the earliest possible moment shall be bound by the modified Terms and Conditions.

§ 8. Final provision

Decisions of the Library of Science Team Head shall govern any matters not stipulated under these Terms and Conditions. Their decision may be appealed against to the Director of the Interdisciplinary Centre for Mathematical and Computer Modelling.

Categories
Bez kategorii

Declaration of Accessibility

The Library of Science Platform managed by the Interdisciplinary Centre for Mathematical and Computational Modelling of the University of Warsaw undertakes to ensure the accessibility of its website in accordance with the provisions of the Act of 4 April 2019 on the Digital Accessibility of Websites and Mobile Applications of Public Entities. The accessibility statement applies to the website https://bibliotekanauki.pl and https://editor.bibliotekanauki.pl and their subpages.

Website publication date: 2020-11-30

Date of last significant update: 2021-01-13

Compliance status

The website complies with the Act on Digital Accessibility of Websites and Mobile Applications of Public Entities at the level of WCAG 2.1. AAA, with the following exceptions:

  • some images do not have an alternative text,
  • some elements that open the link in a new window/tab of the web browser do not inform about it,
  • the page has links highlighted only by an underline,
  • some PDF files were created on the basis of poorly prepared Word documents (there is no well-marked logical structure, tags), or are scans of documents. The way of adding publications in the system reduces such practices to a minimum, however the website is supplemented on a daily basis by a large group of editors and publishers who do not always format files correctly. ICM administrators make every effort to ensure that new documents are prepared correctly.
  • documents that are unreadable by screen readers can be recognized with the OCR tool.

Preparation of the accessibility declaration

The declaration was made on: 2021-01-14.

The declaration was drawn up on the basis of self-assessment by a public body.

Keyboard shortcuts

You can use standard keyboard shortcuts on the website.

Feedback and contact details

In case of problems with the accessibility of the website, please contact the managing authority – the Interdisciplinary Centre for Mathematical and Computational Modelling of the University of Warsaw (e-mail: lp.ik1652725303uanak1652725303etoil1652725303bib@k1652725303sedpl1652725303eh1652725303, phone no.: (22) 874 91 00). In the same way, you can submit requests for access to information that is not available and complain about the lack of accessibility.

Everyone has the right to request the digital accessibility of a website, mobile application or any element thereof. You can also request information through an alternative means of access, such as reading a digitally inaccessible document, describing the content of a movie without audio description, etc. The request should contain the details of the person making the request, an indication of which website or mobile application is meant and the method of contact. Where the requesting person requests information by an alternative means of access, the person should also specify a manner in which the information is to be presented that is convenient for the person. The public entity should comply with the request immediately, no later than within 7 days from the date of the request. If it is not possible to meet this deadline, the public entity shall immediately inform the requester when it will be possible to comply with the request, but this period may not be longer than 2 months from the date of the request. Where it is not possible to ensure digital accessibility, a public body may propose an alternative way of accessing the information. In the event that a public entity refuses to comply with a request for accessibility or an alternative means of access to information, the requester may lodge a complaint about the digital accessibility of a website, mobile application or element of a website or mobile application. Once the above procedure has been used, the person can also submit a request to the Ombudsman.

Categories
Bez kategorii

API OAI-PMH Documentation

API OAI-PMH

Introduction

The platform provides three data repositories compliant with the OAI-PMH specification, one for each type of publication:

These repositories respond to HTTP requests like GET and POST and return responses like text/xml.
Each request to the repository must contain the parameter verb, which determines the type of response.

Identify

The request with the parameter verb with value Identify lets you get basic information about the repository, such as its name, how deleted records are handled, date granulation, ID format, and more. Such requests do not require any additional parameters.

Example

  • URL: https://bibliotekanauki.pl/api/oai/articles?verb=Identify
  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T00:01:20.579837Z</responseDate>
    <request verb="Identify">https://bibliotekanauki.pl/api/oai/articles</request>
    <Identify>
        <repositoryName>Biblioteka Nauki - repozytorium artykułów</repositoryName>
        <baseURL>https://bibliotekanauki.pl/api/oai/articles</baseURL>
        <protocolVersion>2.0</protocolVersion>
        <adminEmail>lp.ik1652725303uanak1652725303etoil1652725303bib@n1652725303imda1652725303</adminEmail>
        <earliestDatestamp>1990-02-01T12:00:00Z</earliestDatestamp>
        <deletedRecord>persistent</deletedRecord>
        <granularity>YYYY-MM-DD</granularity>
        <description>
            <oai-identifier xmlns="http://www.openarchives.org/OAI/2.0/oai-identifier"
                            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                            xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai-identifier http://www.openarchives.org/OAI/2.0/oai-identifier.xsd">
                <scheme>oai</scheme>
                <repositoryIdentifier>bibliotekanauki.pl</repositoryIdentifier>
                <delimiter>:</delimiter>
                <sampleIdentifier>oai:bibliotekanauki.pl:234</sampleIdentifier>
            </oai-identifier>
        </description>
        <description>
            <friends xmlns="http://www.openarchives.org/OAI/2.0/friends/"
                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                     xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/friends/ http://www.openarchives.org/OAI/2.0/friends.xsd">
                <baseURL>https://bibliotekanauki.pl/api/oai/books</baseURL>
                <baseURL>https://bibliotekanauki.pl/api/oai/chapters</baseURL>
            </friends>
        </description>
    </Identify>
    </OAI-PMH>
    

ListMetadataFormats

The request with the parameter verb with value ListMetadataFormats provides the information about the supported metadata formats. The articles repository provides records in the following formats:

  • DublinCore compliant with the requirements of the OpenAire project
  • JATS
  • BWMETA

In the books repository and in chapters the JATS (Journal Article Tag Suite) format has been replaced with BITS (Book Interchange Tag Set) format. The requests ListMetadataFormats do not require any additional parameters.

Example

  • URL: https://bibliotekanauki.pl/api/oai/articles?verb=ListMetadataFormats
  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T00:01:20.579837Z</responseDate>
    <request verb="ListMetadataFormats">https://bibliotekanauki.pl/api/oai/articles</request>
    <ListMetadataFormats>
        <metadataFormat>
            <metadataPrefix>oai_openaire</metadataPrefix>
            <schema>https://www.openaire.eu/schema/repo-lit/4.0/openaire.xsd</schema>
            <metadataNamespace>http://namespace.openaire.eu/schema/oaire/</metadataNamespace>
        </metadataFormat>
        <metadataFormat>
            <metadataPrefix>jats</metadataPrefix>
            <schema>https://jats.nlm.nih.gov/archiving/1.2/xsd/JATS-archivearticle1.xsd</schema>
            <metadataNamespace>http://jats.nlm.nih.gov</metadataNamespace>
        </metadataFormat>
        <metadataFormat>
            <metadataPrefix>bwmeta</metadataPrefix>
            <schema>http://yadda.icm.edu.pl/bwmeta-2.1.0.xsd</schema>
            <metadataNamespace>http://yadda.icm.edu.pl</metadataNamespace>
        </metadataFormat>
    </ListMetadataFormats>
    </OAI-PMH>
    

ListSets

The request with the parameter verb with value ListSets allows you to get information about the hierarchy of collections in the specified repository. Currently the collections are supported only in the articles repository. The request ListSets in this repository responds with a flat hierarchy of collection, each set corresponding with one journal. Other repositories do not support sets – the functionality of the sets is described as optional in the OAI-PMH specification – and current implementation responds with the appropriate error code (noSetHierarchy). This situation may change in the future.

Example

  • URL: https://bibliotekanauki.pl/api/oai/articles?verb=ListSets
  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T00:01:20.579837Z</responseDate>
    <request verb="ListSets">https://bibliotekanauki.pl/api/oai/articles</request>
    <ListSets>
        <set>
            <setSpec>1</setSpec>
            <setName>Prace Instytutu Badawczego Leśnictwa</setName>
        </set>
        <set>
            <setSpec>2</setSpec>
            <setName>Innowacyjne Mleczarstwo</setName>
        </set>
        <set>
            <setSpec>3</setSpec>
            <setName>Diagnostyka Laboratoryjna</setName>
        </set>
    
        <!-- Remaining records... -->
    
    </ListSets>
    </OAI-PMH>
    
  • URL: https://bibliotekanauki.pl/api/oai/books?verb=ListSets

  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T00:01:20.579837Z</responseDate>
    <request verb="ListSets">https://bibliotekanauki.pl/api/oai/books</request>
    <error code="noSetHierarchy">The repository does not support sets.</error>
    </OAI-PMH>
    

ListRecords

The request with the parameter verb with value ListRecords downloads the record list with their full metadata in the format indicated with the parameter metadataPrefix. The deleted records are listed in the response only in the form of heading, without the metadata. The parameter metadataPrefix is required and must take one of the values listed in request response tags “ ListMetadataFormats.

Example

  • URL: https://bibliotekanauki.pl/api/oai/articles?verb=ListRecords&metadataPrefix=jats
  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T00:01:20.579837Z</responseDate>
    <request metadataPrefix="jats" verb="ListRecords">https://bibliotekanauki.pl/api/oai/articles</request>
    <ListRecords>
        <record>
            <header>
                <identifier>oai:bibliotekanauki.pl:105</identifier>
                <datestamp>2020-12-09T23:17:11.424Z</datestamp>
            </header>
            <metadata>
                 <!-- Metadata in selected format... -->
            </metadata>
        </record>
        <record>
            <header status="deleted">
                <identifier>oai:bibliotekanauki.pl:107</identifier>
                <datestamp>2020-12-09T23:17:12.235Z</datestamp>
            </header>
        </record>
    
        <!-- Remaining records... -->
    
    </ListRecords>
    </OAI-PMH>
    

ListIdentifiers

The request with the parameter verb with value ListIdentifiers works like ListRecords, but downloads only headers of the records, without the metadata. The parameter metadataPrefix is required and must take one of the values listed in the indication response to request tags “ ListMetadataFormats.

Example

  • URL: https://bibliotekanauki.pl/api/oai/articles?verb=ListIdentifiers&metadataPrefix=jats
  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T00:01:20.579837Z</responseDate>
    <request metadataPrefix="jats" verb="ListIdentifiers">https://bibliotekanauki.pl/api/oai/articles</request>
    <ListRecords>
        <record>
            <header>
                <identifier>oai:bibliotekanauki.pl:105</identifier>
                <datestamp>2020-12-09T23:17:11.424Z</datestamp>
            </header>
        </record>
        <record>
            <header status="deleted">
                <identifier>oai:bibliotekanauki.pl:107</identifier>
                <datestamp>2020-12-09T23:17:12.235Z</datestamp>
            </header>
        </record>
    
        <!-- Remaining records... -->
    
    </ListRecords>
    </OAI-PMH>
    

GetRecord

The request with parameter verb with value GetRecord returns information about the record with specific ID. The following parameters are required:

  • metadataPrefix – format of the metadata; must take one of the values listed in the indicators response to request tags “
    ListMetadataFormat,
  • identifier – record ID

Example

  • URL: https://bibliotekanauki.pl/api/oai/articles?verb=GetRecord&metadataPrefix=jats&identifier=oai:bibliotekanauki.pl:202060
  • Response:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-31T22:40:01.254200Z</responseDate>
    <request identifier="oai:bibliotekanauki.pl:202060" metadataPrefix="jats" verb="GetRecord">
        https://bibliotekanauki.pl/api/oai/articles
    </request>
    <GetRecord>
        <record>
            <header>
                <identifier>oai:bibliotekanauki.pl:202060</identifier>
                <datestamp>2021-01-28T18:00:26.736Z</datestamp>
            </header>
            <metadata>
                <article xmlns:xlink="http://www.w3.org/1999/xlink"
                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://jats.nlm.nih.gov"
                         xsi:schemaLocation="http://jats.nlm.nih.gov https://jats.nlm.nih.gov/archiving/1.2/xsd/JATS-archivearticle1.xsd">
                    <front>
                        <journal-meta>
                            <journal-title-group>
                                <journal-title>Bulletin of the Polish Academy of Sciences. Technical Sciences
                                </journal-title>
                            </journal-title-group>
                            <issn pub-type="ppub">0239-7528</issn>
                            <publisher>
                                <publisher-name>Polska Akademia Nauk. Czytelnia Czasopism PAN</publisher-name>
                            </publisher>
                        </journal-meta>
                        <article-meta>
                            <article-categories>
                                <subj-group>
                                    <subject>Engineering and technical sciences</subject>
                                    <subj-group>
                                        <subject>mechanical engineering</subject>
                                    </subj-group>
                                </subj-group>
                            </article-categories>
                            <title-group>
                                <article-title xml:lang="en">Calculations of transport parameters in semiconductor superlattices based on the Greens’ functions method in different Hamiltonian representations</article-title>
                            </title-group>
                            <article-id pub-id-type="doi">10.24425/bpasts.2019.129661</article-id>
                            <contrib-group>
                                <contrib>
                                    <name name-style="western">
                                        <surname>Mączka</surname>
                                        <given-names>M.</given-names>
                                    </name>
                                    <role>author</role>
                                    <xref ref-type="aff" rid="aff-202060-0"></xref>
                                </contrib>
                                <contrib>
                                    <name name-style="western">
                                        <surname>Hałdaś</surname>
                                        <given-names>G.</given-names>
                                    </name>
                                    <role>author</role>
                                    <xref ref-type="aff" rid="aff-202060-0"></xref>
                                </contrib>
                            </contrib-group>
                            <aff id="aff-202060-0">
                                <institution content-type="orgname">Department of Electronics Fundamentals, Rzeszów University of Technology, W. Pola 2, 35-959 Rzeszów, Poland</institution>
                            </aff>
                            <pub-date>
                                <year>2019</year>
                            </pub-date>
                            <abstract xml:lang="en">
                                <p>Two methods for calculating transport parameters in semiconductor superlattices by applying Green’s functions are compared in the paper. For one of the methods, the Wannier functions method, where computations in the complex space and Wannier functions base are required, the Hamiltonian matrix is small in size and its elements depend solely on the energy. For the real space method, as it operates in the floating point domain and uses the Hamiltonian containing the elements dependent both on energy and position, the Hamiltonian matrix is larger in size. The size makes the method computationally challenging. To find the consequences of choosing one of the methods, a?direct comparison between the computations, obtained for both methods with the same input parameters, was undertaken. The differences between the results are shown and explained. Selected simulations allowed us to discuss advantages and disadvantages of both methods. The calculations include transport parameters such as the density of states and the occupation functions, with regard to scattering processes where the self-consistent Born approximation was used, as well as the spatial distribution of electron concentration for two superlattices structures. The numerical results are obtained within the non-equilibrium Green’s functions formalism by solving the Dyson and the Keldysh equations.</p>
                            </abstract>
                            <volume>67</volume>
                            <issue>3</issue>
                            <issue-id>11320</issue-id>
                            <fpage>631</fpage>
                            <lpage>641</lpage>
                            <kwd-group xml:lang="en">
                                <kwd>semiconductor superlattices</kwd>
                                <kwd>NEGF formalism</kwd>
                                <kwd>Wannier functions</kwd>
                            </kwd-group>
                            <kwd-group xml:lang="pl">
                                <kwd>nadprzewodnik</kwd>
                                <kwd>półprzewodnik</kwd>
                                <kwd>Formalizm</kwd>
                                <kwd>funkcja Wanniera</kwd>
                            </kwd-group>
                            <self-uri xlink:href="https://3pn.icm.edu.pl/api/full-texts/2020/12/10/086565f1-13e0-40cb-8108-9eb9d85e5d7f.pdf" content-type="application/pdf"></self-uri>
                        </article-meta>
                    </front>
                </article>
            </metadata>
        </record>
    </GetRecord>
    </OAI-PMH>
    

Paging results (resumption token)

In the situation when the number of records that meet request conditions ListRecords, ListIdentifiers or ListSets is higher than the maximum number of records supported in one response, this response will contain the resumption token, which has to be used for the next request. The result of this request will be another part of data that meets the conditions. This step has to be taken until the response will not contain the resumption token.

Parameter resumptionToken is the exclusive type, which means that it has to appear in the request independently. Using the other parameters along with resumptionToken is forbidden. This limitation does not apply to the parameter verb, which must be a part of every request sent to API.

Example

  • We make the first request ListRecords
    • URL: https://bibliotekanauki.pl/api/oai/articles?verb=ListRecords&metadataPrefix=jats
  • We receive the response with part of the records that meet the request conditions and with the value resumptionToken:
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T22:05:03.984324Z</responseDate>
    <request metadataPrefix="jats" verb="ListRecords">http://bibliotekanauki.pl/api/oai/articles</request>
    <ListRecords>
        <record><!-- record data --></record>
        <record><!-- record data --></record>
        <record><!-- record data --></record>
        <!-- ... -->
        <resumptionToken expirationDate="2021-01-01T23:05:03.978Z">
            eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJtZXRhZGF0YVByZWZpeCI6ImphdHMiLCJleHAiOjE2MTIxMzQzMDMsImlhdCI6MTYxMjEzMDcwMywic3RhcnRpbmdJZCI6MTY2Mn0.
        </resumptionToken>
    </ListRecords>
    </OAI-PMH>
    
  • We make another request ListRecords, this time adding the parameter resumptionToken.
    • URL: https://bibliotekanauki.pl/api/oai/articles?verb=ListRecords&resumptionToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJtZXRhZGF0YVByZWZpeCI6ImphdHMiLCJleHAiOjE2MTIxMzQzMDMsImlhdCI6MTYxMjEzMDcwMywic3RhcnRpbmdJZCI6MTY2Mn0.
  • We receive another part of the data and without the token, which means there is no more data that meet the request conditions.
    <?xml version="1.0" ?>
    <OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2021-01-01T22:05:08.435765Z</responseDate>
    <request metadataPrefix="jats" verb="ListRecords">http://bibliotekanauki.pl/api/oai/articles</request>
    <ListRecords>
        <record><!-- record data --></record>
        <record><!-- record data --></record>
        <resumptionToken></resumptionToken>
    </ListRecords>
    </OAI-PMH>
    

Limit the collection of downloaded data (selective harvesting)

The repositories allow to limit the set of data downloaded with the requests ListRecords and ListIdentifiers to data made, modified or deleted in the certain period of time. The parameters from and untilare used for this. These parameters take values in the format defined in the request response tag “ Identify.

Both limitations (inclusive), therefore:

  • Value from needs to be interpreted greater than or equal to,
  • Value until needs to be interpreted less than or equal to.

The articles repository can as well limit the set of data to articles from a certain journal with the parameter set (see chapter ListSets).

Example

  • The headings of the made, modified or deleted records from 1st of January 2019:
    • https://bibliotekanauki.pl/api/oai/articles?verb=ListIdentifiers&metadataPrefix=jats&from=2019-01-01
  • The headings made, modified or deleted until 2nd of December 2020:
    • https://bibliotekanauki.pl/api/oai/articles?verb=ListIdentifiers&metadataPrefix=jats&until=2020-12-02
  • Records made, modified or deleted from 1st of January 2021 and 1st of February 2021:
    • https://bibliotekanauki.pl/api/oai/articles?verb=ListRecords&metadataPrefix=jats&from=2021-01-01&until=2021-02-01
  • The headings of the records made, modified or deleted from 1st of January 2019 from the journal with the set of ID 2:
    • https://bibliotekanauki.pl/api/oai/articles?verb=ListRecords&metadataPrefix=jats&from=2019-01-01&set=2

Errors

API returns the following errors:

  • badArgument – The request includes invalid parameters, the requested parameter is missing, the parameter occurs repeatedly, or the value of the parameter is invalid.
  • badResumptionToken – the value of the parameter resumptionToken is invalid or the token is invalid.
  • badVerb – the value of the parameter verb is invalid, the parameter occurs repeatedly or does not occur at all.
  • cannotDisseminateFormat – the indicated metadata format is not supported by the repository.
  • idDoesNotExist – Record of the indicated ID does not occur in the repository.
  • noRecordsMatch – no records that meet the conditions defined with parameters from and until.
  • noSetHierarchy – the repository does not support sets.

Additional resources

Categories
Bez kategorii

API Documentation

As part of the project, there were three types of API documentation created:

  • authentication – used to verify users and grant them access rights
  • editing – allowing access to the functions of the application module for managing platform resources
  • repository – used to query the repository for publications, access to repository functions via OAI-PMH and REST protocols.

Authentication and Editing API Documentation

Repository API Documentation

Categories
Bez kategorii

Embedding Library of Science on your own webpage

The Library of Science provides easy, sustainable and free access to scientific publications with their metadata. Using the Library of Science does not require creating an account or installing any special software. Articles are made available as PDF files, and books are also available in PDF as well as in other formats such as EPUB, MOBI oraz XML.

A direct link on your website will contribute to the promotion of Polish science, journals and authors, and will also be useful for academic staff and students looking for valuable scientific literature.

You do not have to restrict yourself to adding only a static text with a link to our Platform on your webpage. Our API allows You to embed the dynamic information, i.e., automatically updated lists of publications selected to meet prescribed criteria.

This mechanism works similarly to embedding e.g., a YouTube player on your own website and consists in placing the following fragment in the code of these pages:

<script src=”https://bibliotekanauki.pl/embedded.js?type=latest&publications=articles&publisher=123&limit=10&nonce=abc”>
* </script>

The above script will show on your page the list of the latest 10 articles available in the Library of Science, published by the Publisher with the specified ID. You can choose from:

  • the latest or most popular (type=latest or type=popular, the latest by default),
  • the type of the publication: articles, journals or books (publications=articles, publications=journals or publications=books, articles by default),
  • showing only certain publisher (publisher=123, the ID of the publisher can be found on webpage https://bibliotekanauki.pl/publishing-companies, where the link to the information about every publisher is shown as a number of the said publisher, like for example for publisher: Czytelnik it is 719 – https://bibliotekanauki.pl/publishing-companies/719; without this number the data will be collected for every publisher),
  • number of publications (limit), by default: 3, max 15,
  • the “nonce” parameter is also available, which can be useful to webmasters for more advanced use of the script

Example of using the list:

Categories
Bez kategorii

Library of Science publisher manual

1 Structure of elements in the system

The Library of Science freely shares full texts of articles published in scientific journals and full texts of scientific books, along with their metadata.

The system includes scientific journal and book resources. All the resources are assigned to publishers and structured as follows:

An appropriate parent structure must exist for each article, chapter and book, e.g. in order to add an article there must be a journal and issue (i.e. book, edition, volume – depending on the convention adopted in a given journal) in which it was published.

2 Basic workflow

Publisher resources (metadata of journals and issues as well as metadata and full texts of publications) are added and managed with the participation of other user roles with the use of operations. An operation is a mechanism designed on the platform that consists in performing a data change proposed by the user, following an approval path. The operation is completed when a change is approved and new content is published on the generally available platform service or where the change is cancelled (and there are no changes to the generally available service).

The system enables users to perform the following operations:

  • adding (e.g. adding a new article);
  • editing (e.g. supplementing metadata of a previously added publication);
  • deleting (e.g. deleting an erroneously added book);
  • transferring (e.g. transferring an article to a proper journal issue).

2.1 Article addition process

2.2 Process of adding a new chapter to a collective work

2.3 Process of adding an authored/co-authored book

3 Users’ roles and permissions

The following users’ roles have been provided in the system:

  • journal editor,
  • journal supervising editor,
  • book editor,
  • publisher administrator,
  • ICM administrator.

Users have the following permissions:

Resources/RolesJournal editorJournal supervising editorBook editorPublisher administratorICM administrator
Articleto add, edit, transfer, delete – initiate an operation, to work on an existing operation as an editor and send it to the journal supervising editor for approval
(transfer between issues does not require approval)
to add, edit, transfer, delete – editor permissions and additionally to work on an existing operation as a journal supervising editor and send it to the ICM administrator for approval or return it to the editor
(deleting cannot be returned to the editor)
no permissionsto add, edit, transfer, delete – journal supervising editor permissionsto add, edit, transfer, delete – journal supervising editor permissions and additionally to work on an existing operation as an ICM administrator, to approve operations and return them to the journal supervising editor
Issueno permissionsto add, edit and delete – initiate an operation, to work on an existing operation as an editor, to approve operations
(deleting requires ICM administrator approval)
no permissionsto add, edit and delete – journal supervising editor permissionsto add, edit and delete – journal supervising editor permissions and additionally to work on an existing operation as an ICM administrator, to approve deleting and transfer issues between journals
Journalno permissionsno permissionsno permissionsto add, edit and delete – initiate an operation, to work on an existing operation as a publisher administrator and send it to the ICM administrator for approvalto add, edit, transfer, delete – publisher administrator permissions and additionally to work on an existing operation as an ICM administrator, to accept operations and return them to publisher administrator as well as to transfer journals between publishers
Authored/Co-authored book, collective workno permissionsno permissionsto add, edit and delete – initiate an operation, to work on an existing operation as a book editor and send it to the ICM administrator for approvalto add, edit and delete – book editor permissionsto add, edit, transfer, delete – book editor permissions and additionally to work on an existing operation as an ICM administrator, to accept operations and return them to the book editor
Publisherno permissionsno permissionsno permissionsto amend the publishers’ datato create and delete publishers’ profiles, amend data
Usersno permissionsno permissionsno permissionsto create and delete users, amend data (of users assigned to a given publisher)to create and delete users, amend data

4 How to add a new journal/issue/article?

4.1 Add new article

The operation of adding an article consists in completing the article metadata form and attaching the file containing its full text. Access path to manually create an add new article operation:

STEP 1: go to the journal list

STEP 2: go to the list of journal issues by clicking the journal title

STEP 3: go to the list of articles in the issue by clicking the issue title

STEP 4: click the Add article button and select the method for adding the article

Depending on the option selected, the operation edition form will be completed:

  • immediately only manually, directly on the operation screen;
  • using the marker, i.e. by “highlighting” the metadata fields in the contents of the full text;
  • using Cermine – a tool for automatic metadata extraction from PDF files and then manually.

4.1.1 Manual completion of article metadata

During the add an article operation, you can enter its metadata, such as:

  • basic information (language of the article, title with translations, scope of pages, type of publication, attachment of a full text of the article)
  • information on persons (name, surname, role, information whether the author is open to correspondence, title/academic degree, e-mail address, ORCID, biography)
  • affiliations
  • dates (publication, receipt, approval, on-line publication) 
  • identifiers (DOI, PMCID)
  • information on the contents (abstract with translations, key words with translations, academic disciplines, publication features, research data link)
  • bibliography
  • additional information

and add a file with the full text in PDF, MOBI, EPUB and ZIP with DocBook XML files inside. Notwithstanding the format, the file size cannot exceed 70 MB.

The add an article operation screen includes both mandatory and optional fields. You can only save, submit or approve a form with all the mandatory fields properly completed. Fields that are always required include: main language of the publication, title, publication type, license, full name of at least one author and full text.
Depending on the optional fields completed by the user, related fields may become mandatory (e.g. when adding key words, indicating their language is mandatory and if you delete key words, indicating the language will no longer be mandatory).

The article will be published in the Library of Science only upon approval of the ICM administrator. Therefore, the add operation should be submitted to the higher-level role – send to supervising editor (3) or forward for publication. Selecting save draft (1) or save and preview draft (2) will result in only the draft version of the metadata entered being saved and the add operation will remain at the same use role (will not be returned to them upon approval). Whereas the cancel operation (4) button irreversibly deletes an operation and its data (NOTE: it is not intended for “closing” work without saving – it can be done simply with the “undo” button in the browser or by clicking other links on the screen).

4.1.2 Adding through Cermine

Adding an article via Cermine lets you initiate many add article operations at once (e.g. all the articles from a given issue).

Having selected the “Start adding article using Cermine” option, the user will move to a screen where they can add file(s) from their computer drive.

Fig. Window for selecting an article from the computer drive

The selected documents will be preliminarily uploaded into the system. At this point it is still possible to delete them or cancel the entire action. After completing the list of files and clicking “Start adding new articles operation”, the mechanism will start recognizing metadata in the files.

Fig. Uploading an article to the server

The selected documents will be preliminarily uploaded into the system. At this point it is still possible to delete them or cancel the entire action. After completing the list of files and clicking “Start adding new articles operation”, the mechanism will start recognizing metadata in the files.

Fig. Uploading an article to the server

An add article operation will be created for every file. The form in this operation will contain the metadata recognized by Cermine and the full text file of the article provided in the process described above. This form may then be modified manually and the operation is subject to acceptance just like other similar operations.

Remember that every article should constitute a separate PDF file (the size of the file cannot exceed 70 MB).

The Cermine mechanism provides great support for the user with data entry, but cannot replace the user. In each case, data uploaded in this manner should be verified by the user.

4.1.3 Adding using the Marker

This way of adding publications allows you to select fragments of full text of an article and automatically assign them to individual form fields. This option is similar to marking up fragments of text with colorful markers. 

After clicking the “Start the Marker add operation” option, the user will be redirected to the form screen with a text field and a list of colored field representations of the actual article form. The text field is used to copy contents from the full text of the article. After selecting some text in the text box, the user can assign the selection to the appropriate form fields in the list. It is possible to clear the screen and change previous assignment if incorrect data was marked.

Fig. Form screen with a text field and a list of colored field representations of the actual article form

Fig. Text of the article with marked labels corresponding to the add article form fields

Clicking the “Create article” button will create a new addition operation that contains the form completed according to the “marker” selection. The user will be redirected to this operation. This form may then be modified manually and the operation is subject to acceptance just like other similar operations.

Fig. Preliminarily completed add article form

4.2 Add new issue

Add issue operations are created manually or automatically in the approved journals, based on the data recognized in the source indicated for import while entering or changing the journal data.

How to start an add issue operation:

STEP 1: go to the journal list

STEP 2: go to the list of journal issues by clicking the journal title

STEP 3: click the Add issue button

Issues are added within individual journals. Using the Add Issue button, the user may start adding an issue with the metadata set suggested by the system (year and number) or start to work on an empty form. During the add issue operation, you can specify metadata, such as:

  • year (mandatory field),
  • volume,
  • number,
  • OAI/PMH source (linking the issue with the import source indicated in the journal form – see the Import mechanism chapter),
  • cover.

The cover file cannot be larger than 1 MB and it must be in one of the permitted formats (jpg, png, gif). There are no minimum values for the dimensions and resolution of the file, however it is recommended to check the appearance of the particular cover on the publicly available part of the Platform.

The add issue operation does not have to follow the full approval path (the user initiating the operation can approve it immediately) and it will be visible in the system right after being approved. Only those issues that are not empty, i.e. issues with approved articles, are displayed in the public part of the website.

4.3 Add new journal

The operation of adding a journal consists in completing the journal metadata form. Adding a journal is an operation subject to the ICM administrator’s approval.

When adding a journal, you can specify its metadata, such as:

  • basic information (title with translations, ISSN, DOI, license, scientific disciplines, journal language, publication frequency, OAI-PMH source);
  • journal description (description, editorial office, scientific board, information for authors and reviewers, publishing ethics, open access policy); 
  • indexation and indicators (databases where the journal is indexed, ministerial scoring, ratings achieved by the journal);
  • contact for the journal (journal editorial office contact details and web information on the journal).

OAI-PMH source
Indicating the source for importing the journal resources (metadata and full texts) allows for enabling the import mechanism (see the Import mechanism chapter). This piece of metadata is publicly visible at the bibliotekanauki.pl website and it is only used for handling automatic import operations.

Completing all the journal metadata allows for not only the journal resources, but also the information needed by individuals, such as authors interested in publishing in the journal or people who evaluate journals, to be presented on the Platform.

5 How to add a book, collective work and chapter?

5.1 Add new book

Adding a book involves completing a metadata form and attaching files with the full text of the book. Adding a book is an operation subject to the ICM administrator’s approval.
To start an add book operation, select the Add book button on the book list and select Start adding an authored/co-authored book.

During the add a book operation, you can specify its metadata, such as:

  • basic information (language of the book, title with translations, type of publication, attachment of a cover and full text of the book – only in the case of authored books)
  • dates (publication, receipt, approval, on-line publication)
  • information on persons (name, surname, role, information whether the author is open to correspondence, title/academic degree, e-mail address, ORCID, biography)
  • affiliations
  • identifiers (ISBN, DOI, PMCID)
  • information on the content (number of pages, place of issue, summary with translations, keywords with translations, academic disciplines, publication features, research data link)
  • index
  • bibliography
  • additional information

and add a file with the full text in PDF, MOBI, EPUB and ZIP with DocBook XML files inside. Notwithstanding the format, the file size cannot exceed 70 MB.

Both mandatory and optional fields are included in the add book screen. You can only save, submit or approve a form with all the mandatory fields properly completed; when you try to force one of these action, the mandatory fields that have not been completed will be highlighted. Fields that are always required include: main language of the publication, title, publication type, license, full name of at least one author, full text and publication year (for books published after 1980 – also the ISBN).

Cover
The cover file cannot be larger than 1 MB and it must be in one of the permitted formats (jpg, png, gif). There are no minimum values for the dimensions and resolution of the file, however it is recommended to check the appearance of the particular cover on the publicly available part of the Platform.

5.2 Add new collective work

The operation of adding a collective work consists in completing the journal metadata form. Adding a collective work is an operation subject to the ICM administrator’s approval.
To start an add collective work operation, select the Add book button on the books list and select Start adding collective work.

During the add a book operation, you can specify its metadata, such as:

  • basic information (language of the publication, title with translations, type of publication, attachment of a cover)
  • dates (publication, receipt, approval, on-line publication)
  • information on persons (name, surname, role, information whether the author is open to correspondence, title/academic degree, e-mail address, ORCID, biography)
  • affiliations
  • identifiers (ISBN, DOI, PMID)
  • information on the content (number of pages, place of issue, summary with translations, keywords with translations, academic disciplines, publication features, research data link)
  • index
  • bibliography
  • additional information

Both mandatory and optional fields are included in the add book screen. You can only save, submit or approve a form with all the mandatory fields properly completed; when you try to force one of these action, the mandatory fields that have not been completed will be highlighted. Fields that are always required include: main language of the publication, title, publication type, license, full name of at least one editor, full text and publication year (for books published after 1980 – also the ISBN).

Collective work does not include the full text. Full-text files are added to the individual chapters.

5.3 Add new chapter

Adding a chapter of a collective work consists in completing the metadata on the add chapter operation screen.To start an add chapter operation, select the Add chapter button on the list of chapters in a collective work.

When adding a chapter, you can specify its metadata, such as:

  • basic information (language of the chapter, title with translations, scope of pages, type of publication, license, attachment of a full text of the chapter)
  • information on persons (name, surname, role, information whether the author is open to correspondence, title/academic degree, e-mail address, ORCID, biography)
  • affiliations
  • dates (publication, receipt, approval, on-line publication) 
  • identifiers (DOI, PMCID)
  • information on the content (summary with translations, key words with translations, academic disciplines, publication features, research data link)
  • bibliography
  • additional information

and add a file with the full text in PDF, MOBI, EPUB and ZIP with DocBook XML files inside. Notwithstanding the format, the file size cannot exceed 70 MB.Both mandatory and optional fields are included in the add chapter screen. You can only save, submit or approve a form with all the mandatory fields properly completed; when you try to force one of these action, the mandatory fields that have not been completed will be highlighted. Fields that are always required include: main language of the publication, title, publication type, license, full name of at least one author and full text.
Depending on the optional fields completed by the user, related fields may become mandatory (e.g. when adding key words, indicating their language is required).

6 Edit

Data entered during a pending add operation may be changed by other users, depending on their authorizations, until this operation is approved (or rejected). If, however, after approval of an article, issue, journal, chapter, collective work or book it is necessary to change the data, another operation needs to be run, namely the Edit operation.

In order to perform an Edit operation, select the Edit option from the drop-down list:

or select the Edit option from the operations list on the Publication details screen:

After selecting the Edit option, the user will be redirected to the Edit operation. The metadata completion form is similar to that for the Add operation, while for articles, chapters, collective work, books and journals the previous version of the metadata is displayed additionally (before changes preview and editable after changes fields are available).

The Edit operation follows the same approval path as the Add operation.

7 Delete

The Library of Science allows to delete a previously published article, issue, journal, chapter, collective work and book. The Delete operation in each case requires acceptance by the ICM administrator. Once approval is obtained, data is deleted and cannot be restored.Similarly as with the Edit operation, the Delete operation may be started for a previously approved publication:

The Delete operation may be initiated from the list level or from the publication details screen (similar to the Edit operation). Until the Delete operation is approved, the version visible (also on the generally available part of the website) is the previously approved document.

8 Import mechanism

Add article operations may be created manually (Chapter 4.1) or automatically through the import mechanism. Journals with correctly configured external source of metadata and full texts may be imported into the Library of Science. Adding imported articles and issues require verification and approval, just like manual operations; it is also possible to change their data manually during the approval process.

During automatic import, new issues are added to the journal and require the user’s approval. Articles may be imported to an issue only once it is approved. The Library of Science will not automatically start importing articles to an unapproved issue.

Imports take place automatically, periodically and/or on request (the import on request button is located on the import screen and it is available for Users with a journal supervising editor or higher authorization level).

The first step on the way to automatic import is providing a link to the OAI/PMH source while completing the Journal form.

Starting the mechanism will cause new items for approval to appear in the issue operations list. Only after their approval by an authorized user (journal supervising editor, publisher administrator, ICM administrator), the mechanism will begin import of articles to the individual issues. These articles will appear on the article list and will await approval by the journal supervising editor, publisher administrator and/or ICM administrator.

The Library of Science supports the OAI/PMH protocol with the JATS metadata format and the best import results are offered for journals made available using the current version of the Open Journal Systems with JATS plugin (https://pkp.sfu.ca/ojs/).

In order to make the data available in JATS format in the OJS system, install and run the appropriate publicly available plugins: https://github.com/pkp/oaiJats/releases/tag/v1_0_1-0 and https://github.com/pkp/jatsTemplate/releases/tag/v1_0_1-0.

Metadata can be completed automatically by using the appropriate data entry schema. Using the JATS specification (available on: https://jats.nlm.nih.gov/archiving/tag-library/1.2/element/arc-elem-sec-intro.html) helps ensure that metadata is properly read, matched and listed in the Library of Science.

If new imported issues do not appear in the system despite the OAI/PMH source being provided or if newly imported articles do not appear in the system despite the issue in the system being linked to the issue found in the source – it is possible that there are technical problems with the operation of the source server or compatibility of the data provided by the server with the formats supported by the Library of Science. Report such problems to ICM at lp.ik1652725303uanak1652725303etoil1652725303bib@k1652725303sedpl1652725303eh1652725303.

Fig. Importer mechanism activity information

The Library of Science is integrated with the legacy indexing databases (AGRO, BazTech, CEJSH, DML-PL and PSDJ). Full-text journals in those databases are regularly imported to the Library of Science. Consequently, for journals using websites such as Bentus or Index Copernicus, it is not necessary to re-enter their data into the Library of Science – the data will be imported through the legacy databases. It is assumed that the Library of Science importer functionality will be extended as part of the system’s development, thus increasing the available direct import options to more systems.

Integration with the databases also works in the opposite direction. Editors of journals that start using the Library of Science app to enter data do not have to continue using their previous apps to enter the data into indexing databases. The ICM team regularly synchronizes the data entered into the Library of Science with the databases.

Categories
Bez kategorii

Library of Science user manual

1 Introduction

The Library of Science platform collects full-text scientific publications shared in the open access model in accordance with global standards. 

Full texts of scientific publications collected on the Platform (scientific journals and books) along with their metadata are publicly available for everyone at bibliotekanauki.pl and through the API.

An internal part of the service, used to manage Platform resources, which includes entering metadata and full texts, is available for publishers and administration representatives (after logging in). For detailed information on joining the Platform, please refer to the “Join our publishers” subpage accessible from the Platform’s homepage.

2 Browsing Platform resources

Browsing Platform resources and downloading content and metadata is possible through a public website at https://bibliotekanauki.pl/ without logging in. Resources are indexed by search engines and easy to download through a public API.

The Platform collects and shares scientific publications provided by publishers under agreements concluded with the administrator, i.e. the Interdisciplinary Centre for Mathematical and Computer Modelling of the University of Warsaw. Scientific books shared in the system also come from the otworzksiazke.pl service and the CeON Repository.

The following resources are available on the Platform:

  • articles published in scientific journals, grouped in chronologically-ordered issues (corresponding to books or volumes);
  • scientific monographs in the form of authored or co-authored books;
  • chapters constituting collective work.

2.1 Homepage

The most important part of the homepage is a search engine that allows to find the desired scientific publication. By using simple or advanced search queries, it is possible to narrow down the results to articles, books (authored, co-authored or collective works) and chapters fulfilling the criteria provided.

The simple search engine allows to set the following search filters: “All”, “In journals” or “In books”. The default setting “All” searches the entire Platform contents. Using the “In journals” filter allows to search for articles only in journals, whereas “In books” – only in books (authored, co-authored, collective works and their chapters).

A phrase entered into a simple search engine is searched not only in metadata of individual publications, but also in their full text files.

Fig. Simple search engine of the Library of Science

The advanced search engine allows to narrow down search results based on the contents of metadata fields: contributors, publication dates, main language of publication, license used, assigned scientific disciplines, keywords, publisher and journal name or ISSN number.

Fig. Advanced search engine of the Library of Science

As an example, completing the contributors field in the advanced search engine will show publications with metadata that includes the phrase entered in the contributors fields. Whereas entering the same phrase in the main field of the search engine will search all metadata fields and the full text. The usefulness of both methods depends on the type of inquiry and metadata quality of the particular scientific publications.

After entering at least three characters in each of the advanced search engine fields (except for contributors), a list of suggestions will be displayed – saved entries that may be searched for in the system. 

By completing more than one field in the advanced search engine, you will receive results meeting all the search criteria provided. On the other hand, entering several phrases in one field will return search results that include at least one of the search phrases.

Advanced search fields:

  • Searching with the use of the contributors field allows to find scientific publications for which a given person was entered into the metadata as an author, reviewer, translator or editor. You can also search this field by entering the scientist’s name, surname or ORCID. Many words may be entered into this field.
  • Filtering by dates allows you to find scientific publications created after or before a selected date or withing a selected dates range (the date entered into the metadata is taken into account).
  • Checking the option “Link to research data” will show publications that include information on the associated research data.
  • Completing the language of publication field will show publications for which the indicated language was defined in metadata. It is possible to select more than one language.
  • In the freedom of use field, the user may ask for the authorship and legal status indicated in the metadata of the searched publications (availability to use in accordance with the rules of permitted use or under an open license). It is possible to select more than one status.
  • By selecting scientific disciplines, you may narrow down the results only to scientific publications from a given discipline (this mechanism is also based on the appropriate metadata fields). It is possible to select more than one discipline at a time.
  • When entering search phrases in the keywords field, the user will receive suggestions what keywords exist in the database and can be selected. Many words may be entered into this field.
  • In the last advanced search engine field, you may enter the name of the publication’s publisher, journal title or ISSN number of the journal from which the publication originates.

2.1.3 Navigating the system

Access to publications is possible by means of navigating through the publishers list. Journals and books published by a given publisher are assigned to them.

Fig. Ordered documents structure on the Platform

Moreover, the user can also browse lists of journals indexed in the individual databases, e.g.: Agro database journals (see Databases section).

Each publisher has a separate subpage on the Platform (details screen), featuring their metadata and tabs with lists of journals and books issued.

The details screen for each journal on the Platform has the form of a full card, which gathers information on this journal and articles published in it grouped by subsequent issues in a reader-friendly way.

While navigating, a breadcrumbs menu is visible in the upper part of the screen, which provides an additional way to move between document tree nodes.

The central part of the homepage displays the latest (i.e. the latest added to the Platform) and the most popular (most frequently downloaded in the last 365 days) books, articles and journals. By default, the tab “All (disciplines)” is used, which means that the latest and most popular books, articles and journals visible on the website are selected from the entire Platform resources. Selecting only one discipline, e.g. “Humanities”, will restrict this set only to publications, whose metadata indicate disciplines from the scope of “Humanities”.

Fig. The latest books, articles and journals on the homepage

Fig. The most popular books, articles and journals on the homepage

2.1.5 Databases

The homepage “Databases” section features links that allow to display lists of journals currently available on the Platform and grouped by indexing databases.

The Library of Science Platform only shares those publications that contain full texts and are covered by appropriate agreements signed between publishers and the Interdisciplinary Centre for Mathematical and Computer Modelling of the University of Warsaw. Thus, the above-mentioned lists do not include journals available in those databases that only provide metadata. The databases themselves are maintained as external websites:

  • AGRO (journals on natural and agricultural sciences) http://agro.icm.edu.pl/, 
  • BazTech (journals on engineering and technology, as well as exact sciences) http://baztech.icm.edu.pl/, 
  • CEJSH (journals on humanities, social sciences, theological sciences and arts) http://cejsh.icm.edu.pl/, 
  • DML-PL (journals on mathematics) http://pldml.icm.edu.pl/, 
  • PSJD (journals on medical and health sciences) http://psjd.icm.edu.pl/.

Fig. List of databases on the homepage

Fig. List of journals in the CEJSH database

2.1.6 List of publishers

A separate “Publishers” section is available on the homepage. It contains links to detailed information regarding cooperation with the Interdisciplinary Centre for Mathematical and Computer Modelling of the University of Warsaw and to a full list of publishers. Additionally, six publishers sharing their resources on the Platform are presented there. They are displayed in a random order and change after refreshing the page.

Fig. List of publishers on the homepage

Information included in the Platform header:

  • Publishers – a list publishers sharing their resources on the Platform;
  • About Library of Science – information about the service connected with the project that resulted in the creation of the Platform
  • Help – link to this documentation;
  • Contact – information on how to contact website support;
  • Join Publishers – detailed information on establishing cooperation with the Interdisciplinary Centre for Mathematical and Computer Modelling of the University of Warsaw.

Fig. Library of Science website header

The following information is available in the Platform footer:

  • logotypes of institutions that contributed to starting the project to create the Platform;
  • About Library of Science – information connected with the project that resulted in the creation of the Platform;
  • Privacy Policy – a document providing for the disclosure obligation resulting from the Personal Data Protection Act, Telecommunication Act and (from May 2018) the GDPR;
  • Accessibility – a document regarding the accessibility of a website or mobile application for individuals, which is required under the Digital Accessibility Act;
  • Terms of Service – a document establishing the rules for using the Library of Science;
  • Report error – redirects to the user’s e-mail service to report errors noticed on the Platform or the user’s own initiatives;
  • Contact – information on how to contact the website support.

Fig. Library of Science website footer

2.2 Search results

By default, search results are displayed by relevance in descending order. This means that the entries most relevant to the search phrase are listed at the top. User may sort the results both by relevance and publication date (in ascending and descending order). You may also set the number of results displayed per page in order to adjust the website to your preferences. 

Fig. Search results

The number of filters used will appear next to the Advanced search option.

Fig. Number of filters in the advanced search engine

You may navigate from the search results to searching with a contributor or discipline filter. When you click a contributor’s name and surname on the search list, a list of publications connected with that contributor will be displayed.

Fig. A suggestion for advanced search of publications related to the contributor

Fig. Search results with the contributor filter

Searching by discipline functions in a similar way.

Fig. A suggestion for advanced search of publications related to
the contributor

Fig. Search results with the discipline filter

Additionally, on the publisher’s page, the user can search publications related only to that publisher. After entering the desired phrase in the search engine field, the user will be redirected to the advanced search screen – the phrase will be moved to the main search engine field and the name of the publisher – to the Publisher, journal, ISSN field. 

Fig. Searching items connected to a particular publisher

Fig. Advanced search with the publisher field completed

Searching for items connected to a particular journal functions in a similar way.

2.3 Platform resource pages

The Platform’s resources include metadata sets: text (optionally translated into other languages) and graphics (covers, logotypes), as well as full texts ordered to match the logic structure of documents.

2.3.1 Publisher details screen

The publisher details screen presents, among others, the publisher’s name, description and contact details, as well as their logo, Open access policy and links to the publisher’s websites. 

Apart from the general information tabs, publishers’ pages also include tabs with list of their journals and books.

Fig. Publisher details screen

2.3.2 Journal card

The subpage with a journal’s details screen is considered to be its card, gathering information on the journal in one place and presenting them in a transparent manner. The individual journal card tabs include, among others:

  • a journal overview;
  • a list of issues ordered chronologically from the newest to the oldest;
  • data on the journal’s indices and databases in which the journal is indexed;
  • editorial office contact details;
  • information for journal authors and reviewers.

Fig. Journal card

2.3.3 Issue details screen

The page dedicated to a particular issue includes its metadata and a list of articled included in the issue.

Fig. Issue details screen

2.3.4 Collective work details screen

The page dedicated to a collective work includes its metadata and a list of its chapters.

Fig. Collective work details screen

2.3.5 Scientific publications details screens

The individual scientific publications, including articles, authored (coauthored) books and collective works, along with their chapters, have dedicated subpages with all the metadata entered by the authorized users and full text versions. Individual works may be available in one or several formats: articles in PDF format, whereas books and chapters may be available as PDF, MOBI, EPUB and ZIP archives with DocBook XML files.

Fig. Formats in which books and chapters may be available on the Platform

2.4 Citations

Publications details screens offer the possibility to download a pre-drafted citation and export bibliographical data. Citations are available in five formats: two Harvard formats (APA and MLA), two Vancouver formats (AMA and NLM) and in the format consistent with the Polish citation standard ISO 690. 

Export is available in BIB (supported by BibTEX) and RIS (supported by Endnote, Refman, Procite) formats.

Fig. Citation window

2.5 Export to PBN

The Library of Science Platform allows for an automatic export of the publication to the Polish Scientific Bibliography (Polska Bibliografia Naukowa, PBN) portal. This functions allows to fulfill the requirement of sending scientific publications to the POL-on Science and Tertiary Education Integrated Information System. Launching export of individual publications from the website level redirects the user to the PBN log-in page and initiates the information upload compliant with the requirements of the receiving platform.