Sei sulla pagina 1di 14

LIBRARY MANAGEMENT SYSTEM USING BLOCKCHAIN

Project Review Two

B.E. (Information Technology)


by

ANKITA NAIK (13110 6039)


DIKSHA KULKARNI (161206009)
DEEPSAIEL KAMBLI (131106028)
SUKANYA GOUNDADKAR (151106066)

Information Technology Department


Goa College of Engineering
(Government of Goa)
Goa University
(2018-2019)

1
ABSTRACT
Library management system with blockchain envisions modernized procedures to borrow books
from libraries. Leveraging the blockchain technology, patrons can lend library books directly to
other patrons without bringing it back to the library first. Such transactions can be made regardless
of the registration library, as long as the patrons are registered with a participating library.
Furthermore, the system supports interlibrary borrowing procedures. Taking into account that our
system aims to extend current library services, implementing such a system allows a more
comfortable and efficient way for patrons to interact with the libraries’ ecosystem.

The current system does not enable the user for security and safety of data transmission, which is
assured in blockchain based applications as blockchain assures security and uses API calls to make
the whole process smooth and efficient. Since the current system seems to be optimal for traditional
use, we start the development by creating such system and then implementing blockchain in place
of the database system which will be the main part of the project.

2
CONTENTS (18)
Title Page No. (14)

Chapter 1: Introduction (14)


1.1 Brief Summary of review one

Chapter 2: Algorithms Used (14)


2.1 Blockchain
2.2 Advantages of Blockchain
2.3 Disadvantages of Blockchain

Chapter 3: Literature Survey (14)

Chapter 4: Workflow Process (14)


4.1 Detail Flow Control
4.2 Advantages of Waterfall Model
4.3 Disadvantages of Waterfall Model

Chapter 5: Requirements Study (14)


5.1 Project Requirement Criterion

Chapter 6: Conclusion (14)

Chapter 7: Bibliography (14)


1. Introduction
1.1 Introduction to Project

In current times, most library systems are still not being digitized, and they reason for it is the ear
of getting the Library data corrupted or stolen by hackers. The traditional systems of LMS are
not that efficient or secure when compared to the upcoming Blockchain technology, which
enables to users to have all the data stores with security and access for it will be given accurately
to the authenticated users only. This project will start building such system using the blockchain
and will become a reference for all the future projects working of blockchain technologies.

4
2. Algorithms Used
2.1 Blockchain

A blockchain is a growing list of records, called blocks, which are linked using cryptography.
Each block contains a cryptographic hash of the previous block, a timestamp, and transaction
data (generally represented as a merkle tree root hash).

By design, a blockchain is resistant to modification of the data. It is an open, distributed ledger


that can record transactions between two parties efficiently and in a verifiable and permanent
way. For use as a distributed ledger, a blockchain is typically managed by a peer-to-peer network
collectively adhering to a protocol for inter-node communication and validating new blocks.
Once recorded, the data in any given block cannot be altered retroactively without alteration of
all subsequent blocks, which requires consensus of the network majority. Although blockchain
records are not unalterable, blockchains may be considered secure by design and exemplify a
distributed computing system with high Byzantine fault tolerance. Decentralized consensus has
therefore been claimed with a blockchain.

2.2 Advantages of Blockchain vs Traditional Databases

1. Decentralized access, no need for the administrator (Ex. Network Admin or


Management) or the administrator tools (Ex. Server side apps or PHPmyadmin) to
manage and control the access to blockchain.
2. Extreme Fault tolerance in Blockchain systems. (Traditional Databases have potential for
vulnerabilities in the system, whereas these are not in blockchain.)
3. Higher scalability when it comes to store transactions and interactions between users
compared to databases. For this projects, we will be storing the transactions of book
lending from one user to other or library to one user.
4. For transactions which demand reliability and robustness which can be trusted by people,
blockchain becomes better option as the chain can be verified by users for any
transactions they want, and they can access the publically available data about it.

2.3 Disadvantages of Blockchain vs Traditional Databases

1. Compared to Databases, Blockchains have slower speed. (Depends on the


Implementation.)
2. Performance Cost and Processing Cost of storing Raw data in blockchain is huge
compared to Databases. This can be reduced by encrypting the data and store decryption
key in blockchain. This is the reason why we are not storing personal user information or
book details in the blockchain, as the blockchain will become slow and unusable after
few entries.

5
3. Literature Survey
3.1 The blockchain and its potential for science and academic publishing

Issue title: NFAIS 2018 Annual Conference: Information Transformation: Open, Global, Collaborative
Guest editors: Bonnie Lawlor
Article type: Research Article
Authors: van Rossum, Joris

Abstract

Blockchain allows for decentralized, self-regulating data, ultimately creating a shared


infrastructure where transactions are saved and stored. Scientific information in its essence is a
large, dynamic body of information and data that is collaboratively created, altered, used and
shared. It lends itself well to the blockchain technology because that technology has the potential
to solve challenges around peer review, irreproducibility, and metrics. Other applications of
blockchain technology such as cryptocurrencies and digital rights management systems also have
a potential relevance for academic publishing.

https://content.iospress.com/articles/information-services-and-use/isu180003

3.2 A Case Study for Blockchain in Healthcare: “MedRec” prototype for electronic health
records and medical research data

Ariel Ekblaw, Asaph Azaria, John D. Halamka, MD, Andrew Lippman, MIT Media Lab, Beth
Israel Deaconess Medical Center

Abstract:
A long-standing focus on compliance has traditionally constrained development of fundamental
design changes for Electronic Health Records (EHRs). We now face a critical need for such
innovation, as personalization and data science prompt patients to engage in the details of their
healthcare and restore agency over their medical data. In this paper, we propose MedRec: a
novel, decentralized record management system to handle EHRs, using blockchain technology.
Our system gives patients a comprehensive, immutable log and easy access to their medical
information across providers and treatment sites. Leveraging unique blockchain properties,
MedRec manages authentication, confidentiality, accountability and data sharing—crucial
considerations when handling sensitive information. A modular design integrates with providers'
existing, local data storage solutions, facilitating interoperability and making our system
convenient and adaptable. We incentivize medical stakeholders (researchers, public health
authorities, etc.) to participate in the network as blockchain “miners”. This provides them with
access to aggregate, anonymized data as mining rewards, in return for sustaining and securing
the network via Proof of Work. MedRec thus enables the emergence of data economics,
supplying big data to empower researchers while engaging patients and providers in the choice to
release metadata. The purpose of this paper is to expose, in preparation for field tests, a working
prototype through which we analyse and discuss our approach and the potential for blockchain in
health IT and research.
https://pdfs.semanticscholar.org/56e6/5b469cad2f3ebd560b3a10e7346780f4ab0a.pdf

3.3 Cryptsubmit: introducing securely timestamped manuscript submission and peer


review feedback using the blockchain

Authors:Bela Gipp University of Konstanz


Corinna Breitinger University of Konstanz
Norman Meuschke University of Konstanz
Joeran Beel Trinity College Dublin
Abstract:
Manuscript submission systems are a central fixture in scholarly publishing. However, with
existing systems, researchers must trust that their yet unpublished findings will not prematurely
be disseminated due to technical weaknesses and that anonymous peer reviewers or committee
members will not plagiarize unpublished content. To address this limitation, we present
CryptSubmit - a system that automatically creates a decentralized, tamperproof, and publicly
verifiable timestamp for each submitted manuscript by utilizing the blockchain of the
cryptocurrency Bitcoin. The publicly accessible and tamperproof infrastructure of the blockchain
allows researchers to independently verify the validity of the timestamp associated with their
manuscript at the time of submission to a conference or journal. Our system supports researchers
in protecting their intellectual property even in the face of vulnerable submission platforms or
dishonest peer reviewers. Optionally, the system also generates trusted timestamps for the
feedback shared by peer reviewers to increase the traceability of ideas. CryptSubmit integrates
these features into the open source conference management system OJS. In the future, the
method could be integrated at nearly no overhead cost into other manuscript submission systems,
such as EasyChair, ConfTool, or Ambra. The introduced method can also improve electronic
pre-print services and storage systems for research data.

https://dl.acm.org/citation.cfm?id=3200370

3.4 Blockchain and its Implications for Libraries

Jeffrey G. Coghill

Laupus Library East Carolina University and Eastern AHEC Library Services, Greenville, NC,
USA

Abstract
This article examines the potential uses for Bitcoin and Blockchain technology in libraries. This
article will also explore legal aspects of smart contracts as a means for paying for electronic
resources.

https://www.tandfonline.com/doi/full/10.1080/15424065.2018.1483218

6
3. Workflow Process
3.1 SDLC Model to be used

This project being an Application oriented project, it’s important to understand the process to
create an application properly, and thus an SDLC Model has to be followed in order to achieve
the desired results. For the project, we are going to be using the waterfall model from SDLC
models.

3.2 Advantages of Waterfall Model

1. Easy to explain to the users.


2. Structured approach.
3. Stages and activities are well defined.
4. Helps to plan and schedule the project.
5. Verification at each stage ensures early detection of errors/misunderstanding.
6. Each phase has specific deliverables.

3.3 Disadvantages of Waterfall Model

1. Assumes that the requirements of a system can be frozen.


2. Very difficult to go back to any stage after it finished.
3. A little flexibility and adjusting scope is difficult and expensive.
4. Costly and required more time, in addition to the detailed plan.

7
4. Requirements Study
4.1 Project Requirement criterion

The current objective of the Requirements study is to understand which technologies are required
to be studied and be implemented for usage.

Selection of a viable framework from available languages: HTML, JS, node.JS, PHP, Python,
Java, VB.net, ASP.net, For Database (MySQL, MondoDB).

1. HTML

Hypertext Markup Language (HTML) is the standard markup language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and JavaScript, it forms a triad
of cornerstone technologies for the World Wide Web.

Web browsers receive HTML documents from a web server or from local storage and render the
documents into multimedia web pages. HTML describes the structure of a web
page semantically and originally included cues for the appearance of the document.

Our analysis: HTML is integral part of the webpage and is to be used extensively for the
project. Also, it is one on the easiest language to start from.

2. Javascript

JavaScript often abbreviated as JS, is a high-level, interpreted programming language. It is a


language which is also characterized as dynamic, weakly typed, prototype-based and multi-
paradigm.

Alongside HTML and CSS, JavaScript is one of the three core technologies of the World Wide
Web. JavaScript enables interactive web pages and thus is an essential part of web applications.
The vast majority of websites use it, and all major web browsers have a dedicated JavaScript
engine to execute it.

Our analysis: Javascript is integral part of the creating dynamic webpage and is to be used
extensively for the project. It is little difficult for beginners, but the applications are huge, and is
used for Node.JS.
3. Node.JS

Node.js is an open-source, cross-platform JavaScript run-time environment that executes


JavaScript code outside of a browser. Typically, JavaScript is used primarily for client-side
scripting, in which scripts written in JavaScript are embedded in a webpage's HTML and run
client-side by a JavaScript engine in the user's web browser.

Node.js lets developers use JavaScript to write Command Line tools and for server-side
scripting—running scripts server-side to produce dynamic web page content before the page is
sent to the user's web browser. Consequently, Node.js represents a "JavaScript everywhere"
paradigm, unifying web application development around a single programming language, rather
than different languages for server side and client side scripts.

Our analysis: Node.js is powerful tool for web server and is commonly used with blockchain
tools. We will use it when blockchain is being developed. (The learning curve for Node.js is
huge, making it hard to implement by first time users.)

4. PHP

PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-
purpose scripting language that is especially suited for web development and can be embedded
into HTML.

PHP code may be embedded into HTML code, or it can be used in combination with various web
template systems, web content management systems, and web frameworks.

Our analysis: PHP, being readily available in web hosting and easier to implement, will be used
as server side language, for our early build.

5. Python

Python is an interpreted high-level programming language for general-purpose programming. It


provides constructs that enable clear programming on both small and large scales.

Python can be used to build server-side web applications. While a web framework is not required
to build web apps, it's rare that developers would not use existing open source libraries to speed
up their progress in getting their application working.
Python is not used in a web browser. The language executed in browsers such as Chrome,
Firefox and Internet Explorer is JavaScript. Projects such as pyjs can compile from Python to
JavaScript.

Our Analysis: Python is not required for web server, as it adds extra layer of learning python
alongside JS for Node.js.

6. Java

Java is a general-purpose computer-programming language that is concurrent, class-based,


object-oriented, and specifically designed to have as few implementation dependencies as
possible. It is intended to let application developers "write once, run anywhere" (WORA),
meaning that compiled Java code can run on all platforms that support Java without the need for
recompilation.

Java web applications are typically not running directly on the server. Java web applications are
running inside a web container on the server.

The container is for Java web applications what the JVM (Java Virtual Machine) is for local
running Java applications. The container itself runs in the JVM.

Our Analysis: Java will have huge overhead for the blockchain implementation (run slow
because for JVM), and will not be used.

7. VB.NET

Visual Basic .NET (VB.NET) is a multi-paradigm, object-oriented programming language,


implemented on the .NET Framework. Microsoft launched VB.NET in 2002 as the successor to
its original Visual Basic language

VB.NET is used to create windows based applications.

Our analysis: No need to learn VB.NET, unless a desktop application is to be designed.


(Alternatives also exist, i.e porting webapps into desktop.)

8. ASP.NET

ASP.NET is an open-source server-side web application framework designed for web


development to produce dynamic web pages. It was developed by Microsoft to allow
programmers to build dynamic web sites, web applications and web services.
Our analysis: ASP.NET has huge limitations over PHP (Needs Microsoft windows server, no
frameworks available for faster use, lesser community support), thus shall not be used in the
project.

9. MySQL

MySQL is an open-source relational database management system (RDBMS) It is an Structured


Query Language. MySQL is a central component of the LAMP open-source web application
software stack (and other "AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL,
Perl/PHP/Python".

Our analysis: Since MySQL is readily available in webhosting and is widely accepted, MySQL
will be used for database management.

10. MongoDB

MongoDB is a free and open-source cross-platform document-oriented database program.


Classified as a NoSQL database program, MongoDB uses JSON-like documents with schemata.

In MongoDB, data is stored in JSON-like documents that can have varied structures. To improve
query speed, MongoDB can store related data together, which is accessed using the MongoDB
query language. MongoDB is schema-free, allowing you to create documents without having to
define the structure of the document first.

Our analysis: MongoDB is great for storing unstructured data, but since we have structured data
(Book transactions and books/User details), we can use MySQL instead.

11
5. Conclusion

Library management system with blockchain envisions modernized procedures to borrow books
from libraries. With such system established in a library, the users can now freely be able to get
the books they want and can use all the online features of the library hassle free and without the
worry of Attacks for hackers. Their data is secured through the usage of blockchain. This would
encourage more users to go digital in the fields of storage and security.

12
6. Bibliography
• Consumer Barometer from Google. Consumerbarometer.com. N.p., 2016.
Web. 23 Nov. 2016.

• Crosby, Michael et al. Blockchain Technology. Berkeley: Sutardja Center


for Entrepreneurship & Technology, 2015. Web. 23 Nov. 2016.

• Foltin, Ira. "Bibliotheksportal: Daten 2015". Bibliotheksportal.de. N.p., 2016.


Web. 24 Nov. 2016.

• Hackett, Teresa. Global Library Statistics. International Federation of


Library Associations and Institutions, 2003. Web. 24 Nov. 2016.

• Horrigan, John B., Lee Rainie, and Dana Page. Libraries 2016. Pew
Research Center, 2016. Web. 23 Nov. 2016.

• Zickuhr, Kathryn, Lee Rainie, and Kristen Purcell. Younger Americans'


Library Habits And Expectations. Pew Research Center’s Internet &
American Life Project, 2013. Web. 23 Nov. 2016.

13

Potrebbero piacerti anche