Code Monkey home page Code Monkey logo

extract-urls's Introduction

Extract-URLs

This project is currently set up to extract URLs from PDf publications in the arXiv corpus and run numerous data analysis programs to understand the use of URLs in the arXiv corpus.

Order of Programs

Some of the programs/scripts require the files from other programs/scripts. The correct order is shown below:

  • extract_urls.py (creates a JSON file of extracted URLs for each directory)
  • get_repo_urls.py (creates repo_urls.json (only files with a repo URL) and all_file_urls.json (all files))
  • data_processing/repo_repeats.sh (outputs the frequency of each URL for each repo)
  • data_processing/dir_urls.py (aggregates the number of URLs per month per repo and creates dir_urls.csv and file_count.csv)
  • data_processing/file_url_counts.py (creates file_url_counts.csv, ecdf_numbers.csv, and ccdf_numbers.csv)
  • data_processing/url_freq.sh (creates URL_frequency.csv)
  • data_processing/multiple_repos.sh (finds files that contain URLs to more than 1 repo and creates multiple_repos.csv)
  • data_processing/multiple_repos_table.py (creates a table of the file and which repos it links to)
  • data_processing/pdf_stats.py (calculates mean, median, and quartiles for the number of repo URLs in a PDF and creates pdf_stats.csv)
  • data_processing/repo_url_counts.py (creates repo_url_counts.csv which contains the URL count for each directory and repo)
  • data_processing/urls_per_file.py (creates urls_per_file.csv which contains the average number of URLs per mopnth for each repo)

extract-urls's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

extract-urls's Issues

Add a license/licenses to this repository to enable reuse

It would be good to have license information for this repository, as otherwise it cannot legally be used, unless written permission is granted on a case-by-case basis.

As this repository contains both code and data, I think you'll probably need at least two different licenses, and a way to describe which one pertains to which contents. A thorough "good practice" way of doing this could be to follow the REUSE 3.0 specs. They come with a tool (https://github.com/fsfe/reuse-tool) that helps set up and validate the licenses. This is a bit of work to set up though.

An easier way would be to add a text file LICENSE.md laying out the license terms.

To decide which license may best suit your needs, I find https://choosealicense.com/ helpful.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.