McSinyx
/
cheese-shop
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update report.tex

This commit is contained in:
casker2209 2020-07-07 18:11:20 +07:00 committed by GitHub
parent 8161d552c6
commit ac3b53cc9d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
report/report.tex
View File

@ -84,10 +84,25 @@ data from package indices.
\section{Data Definition}
\subsection{Entity Relationship Diagram}
\includegraphics[width=0.9\textwidth]{ER Diagram.jpg}
This ER Diagram represents the relationship between each of its entity set of data extracted from projects:
Author(Releases-Contact:Many-One):Within each release,there could be one author,due to data extraction method doesn't support multi-author. Yet an author could have multiple releases under his name
Require(Releases-Dependencies:Many-Many):Every releases would require a number of dependencies,and many dependencies can be used by many releases.
Classify(Releases-Trove: Many-Many): This relationship indicates the relationship between Trove classifier and each releases,with many release could be classified
under one Trove classifier,and a release could be classified by many classifiers
Contain(Releases-Keyword:Many-Many): A release has many keywords,and also a keyword can also be in many releases.
Release(Releases-Distribution:One-Many): Within each releases, a number of distribution(s) would be released. A distribution could relate to only 1 releases,but many distributions could be released in the same releases
\subsection{Database Schema}
\subsubsection{releases}
This entity set represents each releases of the project,include the project and its version. The ID of each releases is the primary key to represent each one of them.
This entity set represents each releases of the project,include the name of the project and its version in addition to summary,homepage and author's email. The ID of each releases is the primary key to represent each one of them.
This release ID is also the foreign key of many primary key in other entity set.
\subsubsection{keywords}
Containing both the ID of the releases and the terminology as primary key,this entity represent the keywords of a specific release.
@ -98,7 +113,7 @@ Specific information of each releases. Containing release ID,summary,homepage an
\subsubsection{trove}
This entity set represent Trove classifiers,identified by its ID.
\subsubsection{classifiers}
Containing the release ID and Trove classifiers ID,this table has the role of linking each release with its Trove classifier
Containing the release ID and Trove classifiers ID,this table has the role of representing the relationship of trove and releases
\subsubsection{Distribution}
This entity set represents the distribution of each releases. With its primary key its release ID along with its filename,each distribution contains the url,python version and the python version it requires,the distribtions it requires and its digests (a dictionary) sha256 and md5