public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Chris LAM <fdq09eca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: converting a .bib file into grouped table with custom attributes
Date: Sun, 12 Jul 2020 22:18:51 -0700	[thread overview]
Message-ID: <m24kqcro04.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <c86cfb53-1149-4b81-a93d-d40a058c5785o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


You can use pandoc-citeproc to convert this into a yaml metadata
list with markdown fields.

pandoc-citeproc -y my.bib

You could then use a custom pandoc template to
create a table from this data.  See
https://pandoc.org/demos.html #37 for an example.

However, pandoc-citeproc will ignore the non-standard
fields, so that's probably not going to be enough for you.


Chris LAM <fdq09eca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Dear all,
>
> I am having a *.bib* file with the following format 
> @article{ploberger2017one,
>   title={One belt, One road--China’s new grand strategy},
>   author={Ploberger, Christian},
>   journal={Journal of Chinese Economic and Business Studies},
>   volume={15},
>   number={3},
>   pages={289--305},
>   year={2017},
>   publisher={Taylor \& Francis},
>   datasrc={Est dolore Lorem},
>   type={labour},
>   review={
>     - consectetur eu magna adipisicing excepteur nisi aliqua in. 
>     - Adipisicing ipsum nostrud adipisicing eiusmod sit.
>     - Occaecat minim aute ex culpa dolor. 
>     - Cupidatat dolore exercitation et ullamco non eu et enim.
>   },
>   findings={
>     - consectetur eu magna adipisicing excepteur nisi aliqua in. 
>     - Adipisicing ipsum nostrud adipisicing eiusmod sit.
>     - Occaecat minim aute ex culpa dolor. 
>     - Cupidatat dolore exercitation et ullamco non eu et enim.
>   }
> }
> note that datasrc, type, review, findings are custom attribute.
>
> I have got over 100 entries in this format and I would like to *convert 
> them into a table in a landscape .docx* with the following template
>
> type | year | author | datasrc | review | findings
>
> can pandoc save me from the heavy lifting?
>
> Thank you.
>
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c86cfb53-1149-4b81-a93d-d40a058c5785o%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m24kqcro04.fsf%40johnmacfarlane.net.


      parent reply	other threads:[~2020-07-13  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  1:58 Chris LAM
     [not found] ` <c86cfb53-1149-4b81-a93d-d40a058c5785o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-07-13  5:18   ` John MacFarlane [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m24kqcro04.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=fdq09eca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).