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 (10.6%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Basic Info
  • Host: GitHub
  • Owner: aNiemack
  • License: gpl-2.0
  • Language: Python
  • Default Branch: main
  • Size: 1.71 MB
Statistics
  • Stars: 0
  • Watchers: 2
  • Forks: 1
  • Open Issues: 7
  • Releases: 0
Created about 1 year ago · Last pushed 12 months ago
Metadata Files
Readme License Citation

README.md

cas502religioustextcrossreferencing_tool-

Team: Andrew Niemack and Joshua Carlin

Project Description

This tool is for taking databases of words from several different religious texts for the purpose of cross-referencing use of words that are related to one another. This tool will draw on databases of both scriptural and extra-scriptural sources to compare and contrast usage of words to both inform and verify the reliability of the translation. Beyond translational use, it would also help inform any study in comparative religion to see how each culture and language treats similar and different concepts. The code for this project was written to facilitate searching for terms across multiple texts and solves the problem of having to coordinate many different databases in order to research a religion comparatively. While this is still feasible, and not necessarily a problem to be solved, it certainly can make the research easier for any would-be scholars of comparative religion.

Anticipated Challenges

One of the technical challenges I anticipate is I’m not sure how much access I will have to databases, and how robust those databases might be. Furthermore, trying to balance translational software with dictionary software will likely require a degree of skill with coding that I do not yet have. It may happen that one or the other will have to be developed at some later stage, or one will be very basic and the other will be more fleshed out. The team consists of myself and Andrew Niemack and considering my being an absolute beginner in coding, I will say that there is a challenge in the team composition as a result of the large discrepancy in skills between myself and what the project might call for. Thankfully, this is an idealized theoretical final product, but the product at the end of this course will likely be a very rough prototype of this. Lastly, one challenge regarding the process that would make collaborating difficult in general is that because this works with a large array of languages, it may require collaboration with databases maintained by a diverse enough group of people that it would be difficult to do on one’s own. Beyond that, collaboration within the team itself could be complicated by differences in opinion of how to organize collation of data or even what data to include, as well as what functionalities to implement and in what order.

Communication Plan

The plan is to talk regularly over slack about each week’s goals and what the assignments will require. When necessary, I would also like to meet over zoom. I assume we will work in a shared space, so we’ll be able to see what the other person is doing with the code. This could change depending on the availability and preferences of anybody I end up working with because of personal communication styles, work styles, or even time zones.

Branching Strategy

For this project when each team member is working on a particular task or issue they will create a working branch off main for the task where they will do the primary work on that task. In cases where one member's work is dependent on the other teammate they can merge with the other working branch to get the necessary updates. When a task or issue is completed then the team member will create a pull request to merge the working branch back into main. This will allow everyone to review and approve the code before pushing to main.

Installation Documentation

Running these commands should start the site

  1. python -m pip install -r requirements.txt
  2. cd textcrossreference
  3. python manage.py runserver

Then go to localhost:8000 in browser to view.

Collaboration Documentation

Should any bugs be found or features found to be needed an issue should be generated on GitHub for me to work on. This can include either features or bugs. Related to this, should anyone wish to contribute they can either send a request to merge, or create an issue detailing what they'd like to work on. Should further collaboration be pursued, the owner of the repository will reach out for further information.

User Documentation

This code is a word search function that will search textual databases for instances of string inputs. It's output should be one of two things; it will either be a word count or it will return the lines of data that include the string you search for depending on which iteration of the code you run.

License

I chose the GNU GENERAL PUBLIC LICENSE, version 2 because it allowed for public use, but did not grant patent use rights, which is something I did not want on this software.

Owner

  • Name: Andrew Niemack
  • Login: aNiemack
  • Kind: user
  • Location: Loveland, CO

Citation (CITATION.cff)

cff-version:
message: "If you use this software, please cite it as below."
authors:
- family-names: "Carlin"
  given-names: "Joshua"
  orcid: "https://orcid.org/0009-0009-8775-4908"
- family-names: "Niemack"
  given-names: "Andrew"
  orcid: 
title: "Comparative Religious Database Tool"
version: "0.1.0"
doi: "10.5281/zenodo.14969511"
date-released: "2025-03-05"
url: "https://github.com/aNiemack/cas502_religious_text_cross_referencing_tool-?tab=readme-ov-file"

GitHub Events

Total
  • Create event: 9
  • Release event: 1
  • Issues event: 11
  • Delete event: 6
  • Member event: 2
  • Push event: 33
  • Pull request event: 8
Last Year
  • Create event: 9
  • Release event: 1
  • Issues event: 11
  • Delete event: 6
  • Member event: 2
  • Push event: 33
  • Pull request event: 8

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 9
  • Total pull requests: 4
  • Average time to close issues: 4 days
  • Average time to close pull requests: 3 days
  • Total issue authors: 2
  • Total pull request authors: 1
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 9
  • Pull requests: 4
  • Average time to close issues: 4 days
  • Average time to close pull requests: 3 days
  • Issue authors: 2
  • Pull request authors: 1
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • Jcarlin117 (7)
  • aNiemack (2)
Pull Request Authors
  • aNiemack (4)
Top Labels
Issue Labels
good first issue (1)
Pull Request Labels

Dependencies

requirements.txt pypi
  • Babel ==2.12.1
  • Django ==5.1.6
  • Jinja2 ==3.1.2
  • MarkupSafe ==2.1.3
  • Pillow ==10.0.0
  • PyYAML ==6.0.1
  • Pygments ==2.16.1
  • QtPy ==2.3.1
  • Send2Trash ==1.8.2
  • anyio ==3.7.1
  • appnope ==0.1.3
  • argon2-cffi ==23.1.0
  • argon2-cffi-bindings ==21.2.0
  • arrow ==1.2.3
  • asgiref ==3.8.1
  • asttokens ==2.2.1
  • async-lru ==2.0.4
  • attrs ==23.1.0
  • backcall ==0.2.0
  • beautifulsoup4 ==4.12.2
  • black ==23.7.0
  • bleach ==6.0.0
  • certifi ==2023.7.22
  • cffi ==1.15.1
  • charset-normalizer ==3.2.0
  • click ==8.1.7
  • comm ==0.1.4
  • contourpy ==1.1.0
  • cycler ==0.11.0
  • debugpy ==1.6.7.post1
  • decorator ==5.1.1
  • defusedxml ==0.7.1
  • executing ==1.2.0
  • fastjsonschema ==2.18.0
  • fonttools ==4.42.0
  • fqdn ==1.5.1
  • idna ==3.4
  • ipykernel ==6.25.1
  • ipython ==8.14.0
  • ipython-genutils ==0.2.0
  • ipywidgets ==8.1.0
  • isoduration ==20.11.0
  • jedi ==0.19.0
  • json5 ==0.9.14
  • jsonpickle ==3.3.0
  • jsonpointer ==2.4
  • jsonschema ==4.19.0
  • jsonschema-specifications ==2023.7.1
  • jupyter ==1.0.0
  • jupyter-console ==6.6.3
  • jupyter-events ==0.7.0
  • jupyter-lsp ==2.2.0
  • jupyter_client ==8.3.0
  • jupyter_core ==5.3.1
  • jupyter_server ==2.7.2
  • jupyter_server_terminals ==0.4.4
  • jupyterlab ==4.0.5
  • jupyterlab-pygments ==0.2.2
  • jupyterlab-widgets ==3.0.8
  • jupyterlab_server ==2.24.0
  • kiwisolver ==1.4.4
  • matplotlib ==3.7.2
  • matplotlib-inline ==0.1.6
  • mistune ==3.0.1
  • mpmath ==1.3.0
  • mypy-extensions ==1.0.0
  • nbclient ==0.8.0
  • nbconvert ==7.7.4
  • nbformat ==5.9.2
  • nest-asyncio ==1.5.7
  • networkx ==3.1
  • notebook ==7.0.2
  • notebook_shim ==0.2.3
  • numpy ==1.25.2
  • overrides ==7.4.0
  • packaging ==23.1
  • pandas ==2.0.3
  • pandocfilters ==1.5.0
  • parso ==0.8.3
  • pathspec ==0.11.2
  • pexpect ==4.8.0
  • pickleshare ==0.7.5
  • platformdirs ==3.10.0
  • prometheus-client ==0.17.1
  • prompt-toolkit ==3.0.39
  • psutil ==5.9.5
  • ptyprocess ==0.7.0
  • pure-eval ==0.2.2
  • pycparser ==2.21
  • pyparsing ==3.0.9
  • python-dateutil ==2.8.2
  • python-json-logger ==2.0.7
  • pytz ==2023.3
  • pyvis ==0.3.2
  • pyzmq ==25.1.1
  • qtconsole ==5.4.3
  • referencing ==0.30.2
  • requests ==2.31.0
  • rfc3339-validator ==0.1.4
  • rfc3986-validator ==0.1.1
  • rpds-py ==0.9.2
  • scipy ==1.11.2
  • seaborn ==0.12.2
  • six ==1.16.0
  • sniffio ==1.3.0
  • soupsieve ==2.4.1
  • sqlparse ==0.5.3
  • stack-data ==0.6.2
  • sympy ==1.13.3
  • terminado ==0.17.1
  • tinycss2 ==1.2.1
  • tornado ==6.3.3
  • traitlets ==5.9.0
  • tzdata ==2023.3
  • uri-template ==1.3.0
  • urllib3 ==2.0.4
  • wcwidth ==0.2.6
  • webcolors ==1.13
  • webencodings ==0.5.1
  • websocket-client ==1.6.1
  • widgetsnbextension ==4.0.8