You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bonschorno, related to Global-Health-Engineering/waste-soil-composting-cape-maclear#1 and working towards using washr for GHE and more generally for anyone, I have realized that it would be better if we included the process of defining "the publisher" in a function rather than creating a fork to replace a few terms.
For the next development cycle (i.e. v.1.1.0 on 01.02.2025) I believe this is the most important feature.
The text was updated successfully, but these errors were encountered:
@bonschorno@yashdubey132: I am still thinking about this. Last week I realized that we can start the entire workflow using:
Create empty repo on GitHub with package name
Clone repo
Use devtools::create(".") in root folder to turn into data package.
This will allow us to remove the step from the publishing guide where people need to use the terminal to connect the local and remote repository.
For the feature described in the title of this issue, I am thinking of doing the following:
Instead of "hardcoding" the name of a organization/user and repo into our templates, could we pull this information from the package itself? For example: I create a data package on my larnsce account and name it fskampala. Any function that produces a template which currently is openwashdata.github.io/datapackage should have placeholders, so that the template is populated with larnsce.github.io/fskampala.
@bonschorno, related to Global-Health-Engineering/waste-soil-composting-cape-maclear#1 and working towards using
washr
for GHE and more generally for anyone, I have realized that it would be better if we included the process of defining "the publisher" in a function rather than creating a fork to replace a few terms.For the next development cycle (i.e. v.1.1.0 on 01.02.2025) I believe this is the most important feature.
The text was updated successfully, but these errors were encountered: