Git Product home page Git Product logo

bibs's People

Contributors

a-kohlhase avatar andreakohlhase avatar comfreek avatar dginev avatar dimpase avatar florian-rabe avatar freifrauvonbleifrei avatar gravitydrowned avatar hundecode avatar jazzpirate avatar jfschaefer avatar jukowski avatar katjabercic avatar kohlhase avatar kwarcbot avatar lambdatotoro avatar m-iancu avatar mcearl avatar pdehaye avatar physikerwelt avatar rappatoni avatar tkw1536 avatar vsarstedt avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

bibs's Issues

pull back crossreferences

The main problem with the current publication list generation process is the crossref field in the bibTeX. This leads to wrong results and inflated counts, see brucemiller/LaTeXML#800 for details. Once this is fixed, we can acually use the publication lists in kwarc.info.

publish the generated XMLs

It would be good to publish the generated *.bib.xml. (and the logs for cleaning up the bib sources) on a branch (normally, you do not want the XML; only the bibTeX).
I suspect that this should be quite easy to do.

kwarc.bib invalid: syntax error

Apparently, kwarc.bib contains a syntax error I cannot see. Perhaps integrating validation in the build process would be a goot mitigation action.

Anyway, running biber --tool -V kwarc.bib gives me

ERROR - BibTeX subsystem: C:\<temp path>\kwarc.bib_6404.utf8, line 43527, syntax error: found ".", expected end of entry ("}" or ")") (skipping to next "@")
INFO - WARNINGS: 1738
INFO - ERRORS: 1

where the indicated line is the one with publisher = {Routledge}, in the following excerpt from the file referenced in the error message above:

@techreport{w3c04:rdf-testcases,
  title = {{RDF} Test Cases},
  institution = {World Wide Web Consortium ({W3C})},
  year = {2004},
  date = {2004-02-10},
  type = {{{W3C} Recommendation}},
  month = {2},
  author = {Jan Grant and Dave Beckett},
  url = {http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/},

}

@book{Harding:FeministStandpoint,
  title = {{The Feminist Standpoint Theory Reader: Intellectual and Political Controversies}},
  publisher = {Routledge},
  year = {2004},
  editor = {Sandra Harding},

}

@book{Harding:FeminismAndMethodology,
  title = {{Feminism and Methodology}},
  publisher = {Indiana University Press},
  year = {1987},
  editor = {Sandra Harding},

}

document the html bibliographies building process in the README.md

We should have a short paragraph in the README.md of master to say that we are building publication listings for persons and projects/systems via LaTeXML and say that to see things you should just go to the gh-pages branch.
Then we should document in a README.md on gh-pages how the generation works.
Otherwises I will always forget.

only re-build the parts that have changes.

I have changed the Makefile so that only the parts XML files are rebuilt that need to be rebuilt.
But the comparison mechanism when things should be built in travis is not updated yet.
Here is what should happen.
kwarcpubs.bib --> rebuild kwarcpubs.bib.xml and pubs
extpubs.bib --> rebuild extpubs.bib.xml
kwarccrossrefs.bib --> rebuild kwarccrossrefs.bib.xml and pubs
extcrossrefs.bib -- rebuild extcrossrefs.bib.xml and pubs

Move to GitHub Actions

We should move away from Travis and instead go to GitHub Actions; this is one of the few repos still using Travis.

Deployment lower-cases titles after a colon (e.g. FrameIT: ... lower case ...)

Example tuples (deployed title, bib source code) from https://kwarc.github.io/bibs/ and this repo:

  • FrameIT: detangling knowledge management from game design in serious games

    {{FrameIT}: Detangling Knowledge Management from Game Design in Serious Games}

  • GLIF: a declarative framework for symbolic natural language understanding

    {{GLIF}: A Declarative Framework for Symbolic Natural Language Understanding}

  • KAT: an annotation tool for STEM documents

    {{KAT}: an Annotation Tool for {STEM} Documents}

Is the lower-casing intended?

The "changes? if no, skip Travis" check produces false negatives

Currently, the deploy.sh script running on Travis abort if it notices that no bib source files have changed in the commit for which Travis is running:

# work only if files actually changed.
git diff --quiet --exit-code "HEAD" "HEAD^" src/ Makefile preamble.bib kwarcpubs.bib extpubs.bib kwarccrossrefs.bib extcrossrefs.bib
if [ $? -eq 0 ];then
echo "Refusing to work: No source files were changed. Exiting normally. "
exit 0
fi;

This procudes too many false negatives when pushing multiple commits at once. In both cases below, Travis only considers the most recent commit.

  • consider two local-only commits, where the first changes a source file, and the second one something else. When pushing those commits (two-in-one), the latter commit will make the script above prematurely abort.
  • consider doing a local commit, then merging upstream changes via git pull, and then pushing.

Probably this is too minor to warrant fixing; feel free to close.

Synchronise with SVN automatically

We should really keep this repository up-to-date from SVN automatically via a POST-commit hook, similar to the one we have for the MMT repository.

@kohlhase What do you think? If needed I can set one up.

error in html generation

e.g.

Wrote dist/html/cjucovschi-thesis.html
src/html/generate-html: line 27: 29362 Segmentation fault: 11  latexmlc $LTOPT --destination=${DIST}html/$i-$j.html ${DIST}tex/$i-$j.tex 2> >(tee ${DIST}tex/$i-$j.ltxlog >&2)

add theses bibliographies.

I have annotated all of kwarcpubs.bib with the three keywords phdthesis, mscthesis, bscthesis, from which I would like to generate four publication gh-pages: the three obivous ones and a combined one.
I guess that this should be easy to do for Tom.

It would be really good to have this soon.

project bibliographies

We have started to use the pubs= feature for project publications, e.g. http://kwarc.github.io/bibs/MaMoReD/ But these bibliographies are only generated from kwarcpubs.bib and *crossrefs.bib. But the projects also have outside publications that need to be cited, and these are (currently) in extpubs.bib and are thus not considered. We could

  • move them kwarcpubs.bib and reinterpret thhttp://kwarc.github.io/bibs/MaMoReD/at as "publications of KWARCies and in projects KWARCies are in"
  • leave them there and build from extpubs.bib as well.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.