1. Project Description
This project aims to design a database system for keeping track of scientific publications, authors, conferences, institutions, reviewers, editors and subscribers. There are different cases that explain the relationship between these entities and there are different constraints for entities and their relationships.
As a general user, subscribers can view, search and filter publications. When they find the publication they are searching for, they can view some information about the publication such as the author, publishment date, download count and some other details. Each subscriber may subscribe to many journals. As they become a subscriber of a journal they can get notifications about the subscribed journal. Subscribers can belong to institutions.
Authors must have a subscriber account to make a submission. Once they have their account and confirmed as an author, they can make publication submission to many journals and conferences. However, each submission can only be published in one conference or a journal.
There is a chain of events during publishment of a submission. After the author/authors make their submissions to conference/journal, first the editor decides whether the submission is suitable for the applied publisher, if the editor finds it unsuitable he/she can reject the submission. If the editor finds it suitable, he/she invites one or more reviewer to peer review the submission for content examination.
Reviewers
Reviewers can accept/deny invitations. Each reviewer must be an expert in the topic of the submission. Reviewers who accept invitations must give a feedback to the editor within the specified time period. According to the feedbacks, the editor may choose to reject the paper, send it for a revision/resubmission or approve the submission. If the editor chooses to send it for resubmission, an author must clarify the changes. If the editor chooses to approve the paper, he/she corrects the grammar, style of the paper and sends it to the author and asks for approval. When the author/authors approve the submission, the publisher publishes the paper at the specified publishment date. Some publications might co-operate with institutions which provide the necessary tools/labs etc.
Publications may have sponsors which provide some research budget to the publication and its authors. Sponsors may have some threshold goals for the publications they sponsored. Some publications which have industrial application can have patents to protect their use of rights. The patent must have a patent id number, patent date, and a publication.
For example, a publication can be written by many authors and can be submitted to many conferences. However, it can be published in a single conference or journal. After the submission, reviewers and editors decide if the submission will be published or not.
Publications which are published in a conference must be presented by its authors and additionally, the editor or reviewer of the publication can also join the presentation. Conferences can have the audience which can be subscribers or other people who want to attend the conference.
2. Project Requirements of Scientific Papers Data Management System Free source code PHP
2.1. Functional Requirements
2.1.1. Reviewer Requirements
Reviewers should be able to
accept/decline peer review invitations from editors, view the submission if they have accepted the peer review invitation, approve or reject the submission by sending a report to the editor.
2.1.2. Editor Requirements
Editors should be able to
examine submissions, reject submissions if the submission is unsuitable for the journal. Ask for the revision of the submission if the submission can be made suitable.
approve the requirements and ask for peer review from more than one reviewers if the submission is suitable for the journal. Approve/reject to publish the submission according to the peer reviewers’ report.
edit the submission for style (citations, references, tables, clarity, grammar etc.) before sending it to publication. Ask authors to approve the final submission.
2.1.3. Author Requirements
Authors should be able to
make new submissions to journals and conferences. Edit their submissions by specifying the changes. Cancel their submissions. View the status of their submissions. Search for publications, institutions, journals, and conferences.
view details of publications, institutions, journals, and conferences. Approve/reject the finalized submission. Demand patent for their publications.
2.1.4. Subscriber Requirements
Subscribers should be able to view publications. Subscribers should be able to subscribe/unsubscribe journals and conferences.
2.1.5. Sponsor Requirements
Sponsors should be able to
make a sponsorship offer to publications. set a sponsorship goal to the publications they sponsored for. set a budget for the publications they sponsored for.
2.1.6. Audience Requirements
An audience should be able to attend conferences.
2.1.7. System Requirements
A system must keep track of how many publications a reviewer is currently working on.
The system should remind reviewers as their feedback deadline gets close.
2.1.8. Pseudo Requirements
MySQL is used for database management. Front-end of the web application will use HTML, CSS, Javascript, Bootstrap, Ajax, and jQuery. PHP will be used to develop back-end.
2.2. Non-functional Requirements Scientific Papers Data Management System Free source code PHP
2.2.1. User-Friendly Interface
Our design will assure a simple way of surfing through the web application. As the domain of users is of science-related fields, yet not all of them are familiar with web technology. Hence, it will provide an easy-to-understand interface to perform all tasks: submitting publications, modifying, assigning, reviewing, searching, etc.
2.2.2. Easy Maintenance
The architecture of our application will follow a modular, layer approach. this approach makes it easier to debug errors and apply future changes.
2.2.3. Reliability
As our system will be used for scientific purposes, it cannot bear errors. The data provided by the application should be true and always consistent. Submissions are not made available to the public until all submission process is finalized. It is not possible to make changes to publications after they are published. Users should be able to access available papers at any time.
2.2.4. Quick Response Time
Quick response time depends on two factors: the time it takes to retrieve a paper related to a search query, and to the size of documents retrieved. For search, we will use algorithms to detect matching papers as fast as possible depending on the similarity of words. Pagination will be used to limit papers retrieved per page view. Pagination can also be applied to a single paper view if it is long. Multimedia that is part of the paper (photos & videos) should load fast, not affecting user experience.
2.2.5. Security
Non-subscribers should not be able to view the content of the application nor download it. Viewers cannot see the pre-publication process/history.
3. Limitations Scientific Papers Data Management System Free source code PHP
An author cannot make a submission to a journal/conference which is not related to the journal/conference topic.
An author must include a revision note to its re-submission. An editor cannot invite someone as a reviewer who is not an expert in submission topic. Reviewers must give their reports within the specified time period.
4. Conclusion Scientific Papers Data Management System Free source code PHP
Scientific Papers Data Management System is a web-based application for managing and viewing scientific publications. Different subscription types such as author, editor, reviewer have different tasks and functionalities to perform. In this report, we tried to propose an overall system. We illustrate the system capabilities in the description of the project. We identified the use cases and functionalities of the system in functional requirements. Also express the non-functional, system and pseudo requirements clearly as possible to propose a well functioning system.
Follow the below links for Project Source Code, Report, and Video demonstration
For project demonstration subscribe to our YouTube Channel – Subscribe. For Source code and report (Paid Service), you can send your details to vtupulse@gmail.com