Federal LCA Commons (FLCAC) content on GitHub is spread across several repositories.
- First, please refer to the Frequently Asked Questions page.
- Have a terminology question? Check out the Glossary.
- The Other Resources page can also help direct you to useful resources.
- If the above resources fail to answer your question, consider opening a new issue or contributing to a discussion thread.
Before opening a new issue or discussion on an FLCAC repo, please first confirm that your concern hasn't already been raised or addressed. Review the lists of issues—both open and closed (e.g., this repo's issues)—and discussions across the subset of FLCAC repos relevant to your issue:
| Topic | Repository |
|---|---|
| Federal Elementary Flow List | fedelemflowlist |
| LCIA methods on the FLCAC | LCIA formatter |
| USLCI | USLCI-content |
| Anything else | FLCAC-docs |
Issues are generally intended to report bugs and request enhancements related to the topic of that GitHub repository. It is helpful if issues have a clear path towards resolution.
- Please apply labels to issues to help keep them organized. The list of labels available in each repository can be viewed via the Labels button on the Issues tab (e.g., uslci-content labels).
- Examples of content ideal for issues:
- Did you find an incorrect flow mapping or conversion factor in the All Mappings file? Post an issue here: fedelemflowlist
- Suggest a targeted enhancement to the FEDEFL.
For topics with a wider scope or where more discussion may be required to reach a resolution, please post it as a discussion topic.
Please apply labels to help keep the discussion list organized. Discussions rely on the same set of repository-specific labels used by Issues (e.g., uslci-content labels).
We appreciate your interest in adding to shared resources for the LCA community!
To contribute content to a repository, please fork it, commit your edits, then open a pull request with a clear description of your work.
The FLCAC Data Curation team is actively reorganizing existing resources and updating guidance to make sure it is clear and accessible. Feedback on these efforts is always appreciated. Thank you!