23.3.3-0.1.2-1.40.10 • Published 1 year ago

space-data-node v23.3.3-0.1.2-1.40.10

Weekly downloads
-
License
ISC
Repository
-
Last release
1 year ago

space data server

Space Data Server is an open-source software package that helps integrators get started including data standards from SpaceDataStandards.org into their workflows. (Demo, under heavy development) The SDS acts as a "waypoint" for ingestion / data services, allowing integrators to ingest data from any source (ex., Celestrak OMM).

More information here.

TODO

  • Install script with service
  • Update server key from Ethereum key
  • Limit / delete based on time || number of files
  • Change 'localspacedata' to another name and fix API docs
  • Add querystring formatting options
  • Get IPFS folder hash published to IPFS and add it to server data
  • Change server data to just read the 'serverinfo.json' file in root, maybe rename it
  • Host manifest.json in local API
  • Change to use default path for Ethereum wallet for compatibility
  • Add a "add default server key" to the Admin Settings UI if the server key isn't trusted yet
  • Add an "export settings" button
  • Add export options for the user
  • IPFS network address node addition to config
  • SPACEDATAPEERS.JSON - File that stores that nodes peers, and runs algo to determine trust of those peers and adds trusted nodes to network
  • Encrypt it!
  • Server goes and gets file from IPFS network address
  • Copies over relevant .vcf files (within config limit)
  • IPFS pinning / unpinning config
  • Data UI
  • Document ingest api {filename}.STD.fbs
  • Data matrix
  • Home page & About Page
  • Data parser service
  • Use vCard for server
  • Add code examples

USER DESIGN

  • User: Member of the space data network
  • Trusted User: Users that can upload signed content to the server. The content then is signed by the server, replacing the original signature by the user.
  • Trusted User Admin: Users that can perform administrative functions on the server.
  • Which Standards are trusted per user

USER WORKFLOW

  • Trusted users are bootstrapped from the config file
  • Server key is NOT a trusted user, unless added manually