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
{{ message }}
This repository has been archived by the owner on Dec 9, 2023. It is now read-only.
should be pluggable as a coordinator zome (so does not change the DnaHash)
should be simple to implement as a #[hdk_extern] which returns a Vec<Assessment> for any given Resource & 'field identifier'.
The idea is to facilitate direct retrieval of raw input data from Resources into separate Dimensions. "Direct" means that this data should come in a 'raw' format, without any prior interpretation having been done on it. 'Field identifier' thus feels to be an appropriate parameter type.
I think we've yet to create a name for this sub-type of Assessment that comes straight from Record data. The intention of this issue stub at this stage is to add to the conversation and requirements gathering around multi-Cell architectures for the Sensemaker and Assessment data.
Other approaches are possible, including an initial batch processing at installation time of all Resources in an Applet. In this case we may opt to compute and store Assessment data within the NH Launcher as part of an initial sync; rather than dynamically translating without storing as in the above proposal.
The text was updated successfully, but these errors were encountered:
DnaHash
)#[hdk_extern]
which returns aVec<Assessment>
for any given Resource & 'field identifier'.The idea is to facilitate direct retrieval of raw input data from Resources into separate Dimensions. "Direct" means that this data should come in a 'raw' format, without any prior interpretation having been done on it. 'Field identifier' thus feels to be an appropriate parameter type.
I think we've yet to create a name for this sub-type of Assessment that comes straight from Record data. The intention of this issue stub at this stage is to add to the conversation and requirements gathering around multi-Cell architectures for the Sensemaker and Assessment data.
Other approaches are possible, including an initial batch processing at installation time of all Resources in an Applet. In this case we may opt to compute and store Assessment data within the NH Launcher as part of an initial sync; rather than dynamically translating without storing as in the above proposal.
The text was updated successfully, but these errors were encountered: