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

Generated site is empty, not showing individual documents #3

Open
ronaldtse opened this issue Feb 26, 2021 · 10 comments
Open

Generated site is empty, not showing individual documents #3

ronaldtse opened this issue Feb 26, 2021 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@ronaldtse
Copy link
Contributor

ronaldtse commented Feb 26, 2021

Generated site is empty, not showing individual documents.

Screenshot 2021-02-26 at 9 59 39 AM

@ronaldtse ronaldtse added the bug Something isn't working label Feb 26, 2021
@ronaldtse
Copy link
Contributor Author

I think @andrew2net @abunashir would know how to get this fixed... Thanks!

@abunashir
Copy link

I suspect this is might be similar to metanorma/sample-ogc-discussion-paper#1, for some reason this flavour doesn't generate RXL format by default, so maybe we would need to include rxl explicitly as output format to the source documents.

@ronaldtse
Copy link
Contributor Author

@abunashir good call. Will check. Thanks!

@ronaldtse
Copy link
Contributor Author

Screenshot 2021-03-02 at 2 47 52 AM

@abunashir I'm only getting one document even though all the RXL files are generated. I suspect this has to do with the filenames, because all of them have the filename document.rxl?

Screenshot 2021-03-02 at 2 48 23 AM

@abunashir
Copy link

Let me have a look and I will get back to you.

@abunashir
Copy link

I had look into this - looks like it is being filtered out by Relaton File, we are trying to select the unique documents based on the document id, but for some reason all of these document doesn't have any id, so all of these three document is being filtered out to one unique document [nil, nil, nil].uniq.

I'm not sure if we need the unique statement there, as the selection block should filter out any other document that doesn't contain biodata or bibitem, but if we do then we have to figure out a way to handle the nil data or use some other attributes that would be present all the time then we can use that. But I think @andrew2net can probably tell it better than me, so I would leave that unto him :)

//cc: @ronaldtse

@ronaldtse
Copy link
Contributor Author

Ping @andrew2net what do we do with non-unique IDs? We have to do something here. Thanks @abunashir for discovering this.

@andrew2net
Copy link

I've put this uniquely filtering in case we have duplicated documents in a directory to concatenate (I don't remember if we have duplicated documents in some site generation repo).
It's possible to remove the filter from relaton-cli without any issues for relaton project.

andrew2net added a commit to relaton/relaton-cli that referenced this issue Mar 7, 2021
@andrew2net
Copy link

Removed the uniquely filtering, try to use relaton-cli v 1.7.1

@ronaldtse
Copy link
Contributor Author

Confirmed fixed. And I have made unique docIDs already. Thanks!

Screenshot 2021-03-09 at 5 54 40 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants