Revisions and Commits
Revisions and Commits
rDCIDX Metadata indexer | |||
D8060 | rDCIDX61b22345e70b Add extrinsic metadata indexer | ||
D8058 | rDCIDXf26b4c8b1ca7 Add support for origin_extrinsic_metadata to the storage | ||
D8055 | rDCIDX151a3b8a2b69 github mapping: Add support for more terms from the Codemeta crosswalk | ||
D8054 | rDCIDX8948c8397251 github mapping: Add support for terms outside the codemeta context | ||
D8053 | rDCIDX9085cae01009 Add minimal GitHub metadata mapping | ||
D8046 | rDCIDXe6b03db91c99 Remove SingleFileMapping from JsonMapping's base classes |
Event Timeline
Comment Actions
I don't think we're "resolving" T2063 until we need to process tasks that can't reasonably be handled by celery. On the other hand, journal clients are sort of a resolution to T2063.
Would a "simple" journal client, which would be able to mangle known metadata types into something that can be fed into elasticsearch be appropriate here?
Comment Actions
On the other hand, journal clients are sort of a resolution to T2063.
Yes, they are. I just want to make sure we explicitly decide to go that way.
Would a "simple" journal client, which would be able to mangle known metadata types into something that can be fed into elasticsearch be appropriate here?
Yes.