spreadsheet-and-data-files-helper

Helper to read, extract and transform data from Spreadsheet files and Data files

https://github.com/phillbet/spreadsheet-and-data-files-helper

Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

✓
CITATION.cff file
Found CITATION.cff file
✓
codemeta.json file
Found codemeta.json file
✓
.zenodo.json file
Found .zenodo.json file
○
DOI references
○
Academic publication links
○
Academic email domains
○
Institutional organization owner
○
JOSS paper metadata
○
Scientific vocabulary similarity
Low similarity (12.7%) to scientific vocabulary

Last synced: 6 months ago · JSON representation ·

Repository

Helper to read, extract and transform data from Spreadsheet files and Data files

Basic Info

Host: GitHub
Owner: PhillBet
License: other
Language: Python
Default Branch: master
Size: 25.4 KB

Statistics

Stars: 0
Watchers: 1
Forks: 0
Open Issues: 0
Releases: 0

Created over 3 years ago · Last pushed over 3 years ago

Metadata Files

Readme Contributing License Code of conduct Citation

Spreedsheet and Data Files Helper

Description

[High-level description, describing what exactly software does.]

Motivation

[Why the software does things the way it does and why it was designed in the first place. What problems are solved by it. Links to publications and comparisons to similar software.]

System requirements

[If the software does make high demand on particular resources, then this should be clearly advertised and explained.]

Install

[This may be described in a separate INSTALL file, but the README must then clearly state this.]

Quick start

[How the first task can be performed with the software, or, in the more extensive documentation, a link to the quick start. Outlines how to quickly get started with the software using a basic yet practical example]

Project website

[Website where the software is described and allows users to obtain it as well as its documentation.]

License

[Defines the set of rules and conditions for people who want to use the software.]

Support contact information

[It should be clear where to go for support, for example a contact e-mail address]

Software quality checklist

[This may describe the state of the code, providing the necessary guidance on which aspects could be improved]

Accessibility

[ ] Unique DOI identifier (Please update identifier and link)
[ ] Version control system

Documentation

[ ] README file

Learnability

[ ] Quick start

Buildability

[ ] INSTALL file

Identity

[ ] Website

Copyright & Licensing

[ ] LICENSE file

Portability

[ ] Multiple platforms
[ ] Browsers

Supportability

[ ] E-mail address
[ ] Issue tracker
[ ] Slack
[ ] Gitter

Analysability

[ ] Source code structured
[ ] Sensible names
[ ] Coding standards - style guides

Changeability

[ ] CONTRIBUTING file
[ ] Code of Conduct file
[ ] Code changes, and their authorship, publicly visible

Reusability

[ ] Source code set up in a modular fashion

Security & Privacy

[ ] Passwords must never be stored in unhashed form

Owner

Name: Phill Betancourt
Login: PhillBet
Kind: user
Location: Tetecala

Website: https://phillbet.com/
Twitter: Phill_Bet
Repositories: 4
Profile: https://github.com/PhillBet

Developer

Citation (CITATION.cff)

cff-version: 1.1.0
message: If you use this software, please cite it as below.
authors:
  - name: RegulonDB
    country: MX
    email: regulondb@ccg.unam.mx
    website: http://regulondb.ccg.unam.mx/
date-released: YYYY-MM-DD
doi: [example: 10.5281/zenodo.1003150]
identifiers: 
  - type: "other"
    value: "[example: mbiotools:RSAT_-_Retrieve_Sequence]"
license: [GPL-3.0-only | Apache-2.0 | MIT ]
repository-code: [URL example: https://github.com/regulondbunam/Components]
title: [example: Components]
url: [URL example: http://regulondbtools.ccg.unam.mx/Components]
version: X.X.X