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
LMF Packages and Collections can have metadata files like README, LICENSE, and citation.bib, but these are not stored in the database. For downloaded files, they will persist in the cache, but the cache is not meant to be a permanent record. Putting big text blobs in the database doesn't seem ideal, either. I'm not sure we even want to store these locally
We could create another data subdirectory for these. Something like .wn_data/project_meta. This might contain package directories with everything but the resource files.
The text was updated successfully, but these errors were encountered:
The easiest solution here is probably to just put them in the database rather than doing something custom. If we're just creating a new table and not modifying an existing one, we can add it without forcing users to rebuild their databases, however they wouldn't have access to the metadata of lexicons inserted before the feature is added.
We could probably have a table for READMEs, one for LICENSEs, and another for citation.bibs. E.g.,
CREATETABLEIF NOT EXISTS licenses (
lexicon_rowid INTEGERNOT NULLREFERENCES lexicons(rowid) ON DELETE CASCADE,
textTEXT
)
LMF Packages and Collections can have metadata files like README, LICENSE, and citation.bib, but these are not stored in the database. For downloaded files, they will persist in the cache, but the cache is not meant to be a permanent record. Putting big text blobs in the database doesn't seem ideal, either. I'm not sure we even want to store these locally
We could create another data subdirectory for these. Something like
.wn_data/project_meta
. This might contain package directories with everything but the resource files.The text was updated successfully, but these errors were encountered: