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
As we also have a internal project that lists databases,
and it would make it much easier for others to also create data cards,
I would argue that we should create an extra package for creating a data card.
The package should contain all the code from docs/datacard.py that is responsible for creating a single data card,
which means leave out the code that lists available databases.
Unfortunately, the name datacards for a corresponding Python package is already taken,
maybe we go with audbcards?
Concerning the name: audbcards is more specific and therefore better - as the code will only be useful in the context of data handled within audb. I am happy with this.
As we also have a internal project that lists databases,
and it would make it much easier for others to also create data cards,
I would argue that we should create an extra package for creating a data card.
The package should contain all the code from
docs/datacard.py
that is responsible for creating a single data card,which means leave out the code that lists available databases.
Unfortunately, the name
datacards
for a corresponding Python package is already taken,maybe we go with
audbcards
?@ChristianGeng any other suggestions?
The text was updated successfully, but these errors were encountered: