helpfulengineering / project-data-platform-ts

Project Data Platform

This is a work in progress.

We are currently attempting to build a website to address broken supply chains, such as occur during natural disasters. This is an attempt to build a website that allows makers and manufacturers to match demand for necessary articles which they can make. This matching of demand to supply is a fundamental human problem that could allow lives to be saved and distress relieved during the serial natuarl disaster that we face.

Technology

At present, we are using Microsoft Azure to build a basic website.

Harry Pierson has explored an AI-based matching of tools and capabilities that are available to tools and capabilities which are are needed to make needed articles.

Volunteers Needed

We need volunteers. Although we can use a wide variety of skills we need:

1. Programmers who can build a website with Azure
2. Front-end programmers who, using Nuxt/Vue/Boostrap, can implement visual components. Apply here: https://helpful.directory/opportunity?id=Software-Developer---Typescript-446
3. AI programmers who can use vector-matching a LLMs to build a robust matching algorithm.

Older Content (Obsolete below this point.)

TypeScript port of orginal Project Data Python Code

Current Website

The current website is implemented with Github Pages.

project-data-platform-ts's Issues

Get the Helpful Engineering Favicon, or create for for this project.

Create supply space query engine and generate Test supply space query result

Create a way to render an OKH within a limited real estate (with one image?) that can be the foundation of a catalog page....

The idea here is to copy something like Amazon, that allows an OKH to be shown at several different resolutions.

We want to render, for example, 10 per page, or 1 per page.

Investigate reading large JSON files directly from GitHub Pages (NOT the Github API) as a means of loading OKHs....

For example, this directory in the repo:

https://github.com/helpfulengineering/library/tree/main/beta/okh

But also @devhawk may have translated a bunch of recipe JSON in an S3 object; but we may be able to do it as a raw file.

Security for this repo

We want security, permissions, and teams for this repo to be the same as the project-data-platform repo.

Allow user to choose a supply space query result and visualize using cytoscape (aka Tim's code)

Read OKHs & OKWs from S3

provide user a mechanism to choose a OKH

Reinstall front-end from azure branch....

Today we were not able to run the front-end, though it ran previous. I believe I removed nuxt or the /dist directory in my github manipulations.

One way or another, we should create a "clean slate" installation of next to attempt to reach our backend. At present, the back end runs locally; we are attempting to reach our storage server in Azure, which we believe we did successfully create.

Copy Documentation GOSQAS to this repo

Port existing python atom code to TypeScript

TypeScript??

Create scaffolding for baseline web app

Develop a draft architecture and implement the necessary frameworks and infrastructure for the architecture.

Install azure function services based documentation

CORS problem of the s3 buckets from the library....

This URL is public and works great:

https://s3.amazonaws.com/github-helpfulengineering-library

...but when called from AJAX within a page, it throws a CORS error:

project-data-platform-ts/:1 Access to fetch at 'https://s3.amazonaws.com/github-helpfulengineering-library' from origin 'https://helpfulengineering.github.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Here is the code:

   // This worked...
    var url = `https://s3.amazonaws.com/${albumBucketName}`;
    fetch(url)
  .then(response => {
    if (!response.ok) {
      throw new Error('Network response was not ok');
    }
    return response.text();
  })
  .then(data => {
    console.log(data); // Do something with the content of the file
  })
  .catch(error => {
    console.error('There was a problem with the fetch operation:', error);
  });

I believe in S3 we may have to set a CORS rule. This reference suggests this:

https://docs.aws.amazon.com/AmazonS3/latest/userguide/cors-troubleshooting.html

I believe in our S3 configuration we need to set the "Access-Control-Allow-Origin" header on the response. I suggest it is safe to set this to "*" for our S3 bucket.

Need a design for the Home Page

Miro Board Link