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
In addition, there are a number of Librivox books after the linked ebook. Github, unfortunately, isn't the best place to keep track of public domain audio books. Next steps are to find ways of identifying these books in the GITenberg collection.
@eshellman Given that folks keep running into them in github search and our own enumeration of the github org, lets remove them entirely. I can't think of any cases where we would need the librivox catalog in this format alongside text book repos.
Adding links to the appropriate librivox recordings would be excellent when someone has the bandwidth. Would a feature request go on the gitberg or metadata repo?
I'm starting to think that it's unwieldy to separate the metadata development from the "gitberg" development. It was certainly a pain to get gitberg running from source while trying to import the metadata sub-module.
I too have had issues getting that to work when developing on gitberg.
Given that the yaml meadata format is our standard, and hopefully one of most usable parts of the gitberg cli. I say we go ahead and merge the two repos but keep separate folders.
Should note that with PR #94 we include repo lists to assist repo-walking code. These would be updated, of course.I'll proceed with deletion over the weekend. Should note that the gitberg tool can be easily deployed to recreate these repos where ever they may be needed. Speak now or forever...
With regard to an issue for librivox links, I vote for adding it to gitberg.
Activity
sethwoodworth commentedon Aug 3, 2014
In addition, there are a number of Librivox books after the linked ebook. Github, unfortunately, isn't the best place to keep track of public domain audio books. Next steps are to find ways of identifying these books in the GITenberg collection.
MasterOdin commentedon Nov 27, 2014
All rdf files have an identifier for what type it is. Here are the types that I've discovered (with an id for example):
These are part of dcterms:type tag.
Running through all the rdf files and just generating the titles + id if not text would give you all GITenberg repos I'd think.
[-]Some PG books are _only_ audiobooks[/-][+]remove PG books that are _only_ audiobooks[/+]sethwoodworth commentedon Mar 3, 2016
@eshellman Given that folks keep running into them in github search and our own enumeration of the github org, lets remove them entirely. I can't think of any cases where we would need the librivox catalog in this format alongside text book repos.
Adding links to the appropriate librivox recordings would be excellent when someone has the bandwidth. Would a feature request go on the gitberg or metadata repo?
eshellman commentedon Mar 3, 2016
I'm starting to think that it's unwieldy to separate the metadata development from the "gitberg" development. It was certainly a pain to get gitberg running from source while trying to import the metadata sub-module.
sethwoodworth commentedon Mar 3, 2016
I too have had issues getting that to work when developing on gitberg.
Given that the yaml meadata format is our standard, and hopefully one of most usable parts of the
gitbergcli. I say we go ahead and merge the two repos but keep separate folders.eshellman commentedon Mar 3, 2016
here is a list of 1,106 repos proposed for removal
https://gist.github.com/eshellman/b8b07b8168adfbe83ae9
eshellman commentedon Mar 3, 2016
Should note that with PR #94 we include repo lists to assist repo-walking code. These would be updated, of course.I'll proceed with deletion over the weekend. Should note that the gitberg tool can be easily deployed to recreate these repos where ever they may be needed. Speak now or forever...
With regard to an issue for librivox links, I vote for adding it to gitberg.