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

One markdown file per document #2

Open
amirouche opened this issue Jun 25, 2019 · 5 comments
Open

One markdown file per document #2

amirouche opened this issue Jun 25, 2019 · 5 comments

Comments

@amirouche
Copy link

amirouche commented Jun 25, 2019

Use the following template and create one markdown per document:

# [Title](https://link/to/document)

By Author1, Author2 and Author3

## Keywords

- abc
- def

## Abstract

abracadabra...


@lassik
Copy link
Member

lassik commented Mar 3, 2020

We can parse the LOSE files (which now also contain the abstracts) to generate Markdown documents like this. Note that there are over 1000 papers, so quite a few .md files!

@lassik
Copy link
Member

lassik commented Mar 3, 2020

Maybe would be best to store only the LOSE forms and conversion scripts in the repo. The scripts can convert to whichever formats people want, and the converted versions can be hosted at convenient websites. Let's keep the current .md files until the LOSE files are stable, though.

@amirouche
Copy link
Author

What do you think about one LOSE file per publication, then we gather with some heuristic those publication into .md?

@lassik
Copy link
Member

lassik commented Mar 8, 2020

In that case there would be more than 1000 LOSE files; we should at least group them into subdirectories by some criteria. Perhaps it makes sense. Each entry already has an (id ...) property such as (id fuchs1985dreme). I guess the filename could be fuchs1985dreme.scm in some subdirectory.

In practice, I've found it very convenient to work with the current organization so far. Though the page names are non-descriptive page1..page11, they are actually organized by topic. I guess we could rename them so the filename describes the topic.

@lassik
Copy link
Member

lassik commented Mar 8, 2020

There's a parser in tools/losebib-read.sld. If we don't parse the topic hierarchy from the file contents, we need to parse it from the directory layout.

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

No branches or pull requests

2 participants