Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / CriticalAssetManagement/CAMS issues and pull requests

#34 - Asset key skills and knowledge along with names and contact details – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: documentation, enhancement

#33 - Asset operator requirements – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question

#32 - Asset approval/regulatory authorities and contact details – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, Discussion

#31 - Asset Inventory: Asset Data Requirements - Asset owner and contact details – T, allow for two owners

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, help wanted

#30 - Asset function or role – initially T, but it will be desirable to create codes for this – C

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, help wanted, question

#27 - Facility to display location of mobile assets of tracked (lat/long – N, and location address – T)

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability

#26 - Asset name (T) and location (lat/long – N, and location address, if used – T, if applicable)

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, sustainability

#25 - Asset Inventory: Linkages between assets should be shown in GIS-Based display

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 2 comments
Labels: enhancement, sustainability

#24 - Include risk of critical staff/skills not being available to operate, repair or enable access to the asset

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement

#23 - Capture any additional mitigation measures that relate to the cascading failure risk (asset linkages), and dates – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: documentation, enhancement, question, sustainability

#22 - For each risk, show potential cascading failure chains (asset linkages) with annotations - C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability, Discussion

#21 - Presence or risk of linkage between any two assets and the nature of that linkage (eg. proximity, dependency, shared dependency) – C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, help wanted, sustainability, Discussion

#20 - Security and Access

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment

#19 - More NFRs

Issue - State: closed - Opened by sreyac almost 3 years ago

#18 - Non-Functional Requirements

Issue - State: closed - Opened by sreyac almost 3 years ago

#17 - Considerations for Inventory and Asset Data

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment

#16 - Emergency Response: Additional

Issue - State: closed - Opened by sreyac almost 3 years ago

#15 - Emergency Response

Issue - State: closed - Opened by sreyac almost 3 years ago

#14 - Asset Risk Mitigation: Additional considerations

Issue - State: closed - Opened by sreyac almost 3 years ago

#13 - Asset Risk Mitigation

Issue - State: closed - Opened by sreyac almost 3 years ago

#12 - Asset Inventory: Linkages between assets

Issue - State: closed - Opened by sreyac almost 3 years ago

#11 - Asset Inventory: Capture consequences of projected loss or damage

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment

#10 - Asset Inventory: Capturing perils to which each asset is exposed

Issue - State: closed - Opened by sreyac almost 3 years ago

#9 - Asset Inventory: Asset Data Requirements

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment

#8 - Adding previous work to new CAMS repository

Pull Request - State: closed - Opened by ErikHsu almost 3 years ago

#7 - Add information and fields to Owner Class

Issue - State: closed - Opened by mdw1715 about 3 years ago

#6 - Data Sources Document

Issue - State: closed - Opened by mdw1715 about 3 years ago

#5 - Funding Source Document

Issue - State: closed - Opened by mdw1715 about 3 years ago

#4 - Asset Updates - What counts as an update

Issue - State: closed - Opened by mdw1715 about 3 years ago
Labels: documentation, help wanted

#3 - Build a integrated interface

Issue - State: closed - Opened by luke-feeney about 3 years ago
Labels: enhancement

#1 - Start the task of creating tickets for the CAMS project

Issue - State: closed - Opened by luke-feeney about 3 years ago
Labels: enhancement