Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

\nocite{*} but with option to select entry by keywords/datatype #186

Closed
maieul opened this issue Nov 25, 2013 · 10 comments
Closed

\nocite{*} but with option to select entry by keywords/datatype #186

maieul opened this issue Nov 25, 2013 · 10 comments
Labels

Comments

@maieul
Copy link
Contributor

maieul commented Nov 25, 2013

Should it be possible to have an equivalent of \nocite{*} but with option select entry by keywords or datatype. It could be useful to don't forget to add in final bibliography entries about one topic.

@aboruvka
Copy link
Collaborator

\nocite accesses bibliographic data. We can't selectively \nocite entries by keyword or entrytype without accessing the data first. You should try filtering the bibliography instead.

@maieul
Copy link
Contributor Author

maieul commented Nov 25, 2013

I see, but filter implies to suppress datas, and what I want is to add datas.

Example :

  • entry A has keyword "X"
  • entry B has keyword "X"
  • Entry C has keyword "Y"

I want to automatically add entries with keyword X, but manually add entry with keyword Y.

If I made \nocite{*}, that implies I should filter C, except if C was explicitly called. But \ifciteseen can't be called only (as documentation says) in bibliography style, not in a bibcheck.

Should'nt be possible to have command which says to biber "add entry if … some condition…) (as nocite{xx} says to biber "add this entries") and biber will filter that ?

@aboruvka
Copy link
Collaborator

Unless an entry has already been previously cited via any citation command, we can't know its keywords or type at the point of \nocite.

You can create a category for cited entries and then define a filter considering this new category and keywords. Use of \nocite{*} is sometimes problematic with \labelnumberwidth when many entries are filtered. To fix this, you can selectively enable the skip* options via biber's sourcemap.

I realize it might be frustrating to have your feature requests continually closed. Instead of requesting a feature to solve each new problem you encounter, consider posting a question at TeX.SE. We often address questions worthy of a new feature here.

@maieul
Copy link
Contributor Author

maieul commented Nov 25, 2013

What I don't understand is : when you use \nocite{*} you did'nt read the data information before, isn't it ? but you said to biber to add data entry to bbl file.

@aboruvka
Copy link
Collaborator

Keywords and types are part of the bibliographic data. These data are available for an entry only after it is cited via \nocite or some other citation command.

Please, if you need help solving your problem post at TeX.SE.

@maieul
Copy link
Contributor Author

maieul commented Nov 25, 2013

Of course, I know keywords and types of bibliographical datas. But I don't understand what forbid to :

  • write in the bcf file "Hey biber, could you add all entry with this keyword"
  • changer biber which understand this "sentence".

When a nocite is used he say "hey, biber, could you add all entry in the bbl file". And biber read all entry and write it in bcf file.

I can understand you don't want to add this feature. But I don't understand why it's not possible.

Ps : with your link, I understand what method you want I use. So here is not a question help, but a question to understand your answer.

@aboruvka
Copy link
Collaborator

Biber and BibTeX have no mechanism for backing out of an entry once it encounters specific keywords. They are just parsers. Biber can perform source mapping, but it can't selectively parse entries.

\nocite is a LaTeX command. From the LaTeX end you can only perform actions on the basis of bibliographic data already available in the bbl file.

@maieul
Copy link
Contributor Author

maieul commented Nov 25, 2013

ok, I understand better. Thanks

@maieul
Copy link
Contributor Author

maieul commented Nov 25, 2013

ps : as you can use, I use also stackexchange … when I think it's a problem of comprehension from mine, and not a need for new feature. http://tex.stackexchange.com/questions/146886/declaredatamodelentryfields-make-biber-doesnt-work

@aboruvka
Copy link
Collaborator

I can see that, but what I am saying is that posting to TeX.SE is generally better use of everyone's time. That way you avoid (1) conceiving a new feature to solve your problem, (2) clarifying what your underlying problem is with additional comments, and (3) having your feature requests rejected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants