search

building-envelope-data / api

API specification to exchange data about building envelopes
MIT License
3 stars 1 forks source link

Rename `ise621` to `building-envelope-data`? #276

Closed simon-wacker closed 2 years ago

simon-wacker commented 2 years ago

The four projects of the organization ise621 are all related to building-envelope-data. I would thus just call the organization building-envelope-data, rename the project building-envelope-data to schema, and leave the other project names as is. What do you think @christoph-maurer ?

simon-wacker commented 2 years ago

Additional Note: An alternative to the project name schema is api. The project currently consists of two API specifications in the form of GraphQL Schemas and a data schema in the form of mutliple JSON Schemas.

christoph-maurer commented 2 years ago

I think it's a good idea to rename ise621 to building-envelope-data and building-envelope-data to api. @simon-wacker How would we update the links in files like README.md and CONTRIBUTING.md in all four repositories?

simon-wacker commented 2 years ago

I'd use SED: sed -i -e "s_ise621/building-envelope-data_ise621/api_g" -e "s/ise621/building-envelope-data/g" *.md and then check whether everything is as intended with git diff.

christoph-maurer commented 2 years ago

We need to update the links from the metabase frontend to Github, too.

simon-wacker commented 2 years ago

Yes, I did that in https://github.com/building-envelope-data/metabase/commit/01540bbc5f40edbeab49e38d2896a10cb509b1f6#diff-286c287cf425c0eafcf41c57c6bccb2ac13ece5bfe5dc5f88d627f703ad7100e but I haven't redeployed the frontend yet. The old URLs will work for some time to come (I believe until someone else claims the old organization name ise621).