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
The Computing external website (computing.llnl.gov) is undergoing a major design & IA overhaul in FY21. It has a new taxonomy of 90+ terms that will be used to relate content to each other. The taxonomy was developed with Computing SMEs.
@IanLee1521 and I discussed comparing our GH tags -- those that drive the software.llnl.gov category browse & those we recommend to aid in repo discoverability -- to the new Comp taxonomy to find overlaps and/or opportunities for streamlining our vocabulary.
Compare portal terms to Comp terms (ask me for LLNL-only OneDrive access to the spreadsheet, "Portal vs Comp compare" tab)
What do we want to do with this information? How much do we care that our GH terms aren't exactly the same as those on Comp? Example: compiler vs compiler technology
(A future Comp feature may leverage the GH API to pull in repo release or download information for open source projects that are featured on the Comp website. The Comp web team has not discussed doing anything with GH topics.)
The text was updated successfully, but these errors were encountered:
The Comp taxonomy will be exposed on browse pages and individual nodes; there won't be a single page listing all the terms, at least not at launch. I need to think about this some more...
The Computing external website (computing.llnl.gov) is undergoing a major design & IA overhaul in FY21. It has a new taxonomy of 90+ terms that will be used to relate content to each other. The taxonomy was developed with Computing SMEs.
@IanLee1521 and I discussed comparing our GH tags -- those that drive the software.llnl.gov category browse & those we recommend to aid in repo discoverability -- to the new Comp taxonomy to find overlaps and/or opportunities for streamlining our vocabulary.
What do we want to do with this information? How much do we care that our GH terms aren't exactly the same as those on Comp? Example:
compiler
vscompiler technology
(A future Comp feature may leverage the GH API to pull in repo release or download information for open source projects that are featured on the Comp website. The Comp web team has not discussed doing anything with GH topics.)
The text was updated successfully, but these errors were encountered: