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

Hardcode v1 authors and remove them from metadata #998

Merged
merged 10 commits into from
Mar 10, 2020
Merged

Conversation

cgreene
Copy link
Member

@cgreene cgreene commented Mar 10, 2020

I tried to pull from @dhimmel's branch associated with #997, make some more updates to better address the complexities, and then push back but I think I must have pushed to the wrong place.

@cgreene cgreene requested a review from dhimmel March 10, 2020 13:15
@AppVeyorBot
Copy link

AppVeyor build 1.0.55 for commit 77a8da6 by @cgreene is now complete. The rendered manuscript from this build is temporarily available for download at:

@cgreene
Copy link
Member Author

cgreene commented Mar 10, 2020

Ok - I'm pretty sure this will work now.

@cgreene cgreene requested a review from agitter March 10, 2020 13:23
@AppVeyorBot
Copy link

AppVeyor build 1.0.57 for commit 8cd7707 by @cgreene is now complete. The rendered manuscript from this build is temporarily available for download at:

@dhimmel
Copy link
Collaborator

dhimmel commented Mar 10, 2020

This doesn't contain the work from #997 yet, but that is OKAY. these two PRs can be merged independently.

I wonder if we should delete the v1 authors in metadata or move them to a field like v1_authors. Deletion is probably okay for now, we can always add them back in the future should we need them.

Looks like the newlines between affiliations have been removed. maybe because no longer a numbered list?

@cgreene
Copy link
Member Author

cgreene commented Mar 10, 2020

Ahh! I was wondering what happened with those newlines. You're right - making the affiliations have a version prefix broke the numbered list. I could make a bulleted list with the numbers after them, add an additional line (though that'd make a paragraph space), or something else. What do you think?

@dhimmel
Copy link
Collaborator

dhimmel commented Mar 10, 2020

Just read about pandoc's example_list extension (example). Don't think we need it.

I could make a bulleted list with the numbers after them, add an additional line (though that'd make a paragraph space), or something else. What do you think?

The easiest solution at the moment would be to add (two spaces) at the end of affiliation lines (same effect as adding <br>).

@cgreene
Copy link
Member Author

cgreene commented Mar 10, 2020

I had no idea that was possible!

@AppVeyorBot
Copy link

AppVeyor build 1.0.58 for commit 38c2e9d by @cgreene is now complete. The rendered manuscript from this build is temporarily available for download at:

@AppVeyorBot
Copy link

AppVeyor build 1.0.59 for commit 031daee by @cgreene is now complete. The rendered manuscript from this build is temporarily available for download at:

Co-Authored-By: Daniel Himmelstein <daniel.himmelstein@gmail.com>
@AppVeyorBot
Copy link

AppVeyor build 1.0.60 for commit ca18e93 by @cgreene is now complete. The rendered manuscript from this build is temporarily available for download at:

content/00.front-matter.md Outdated Show resolved Hide resolved
@AppVeyorBot
Copy link

AppVeyor build 1.0.61 for commit cb20daa by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

@AppVeyorBot
Copy link

AppVeyor build 1.0.62 for commit 6cb5767 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

content/00.front-matter.md Outdated Show resolved Hide resolved
@dhimmel dhimmel changed the title Use random order Hardcode v1 authors and remove them from metadata Mar 10, 2020
@AppVeyorBot
Copy link

AppVeyor build 1.0.63 for commit c4daec3 by @dhimmel is now complete. The rendered manuscript from this build is temporarily available for download at:

Copy link
Collaborator

@dhimmel dhimmel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I'll merge now and we can follow up with additional suggestions.

@agitter
Copy link
Collaborator

agitter commented Mar 15, 2020

What do we want to happen for an author who contributes to v1 and v2 and has a change in competing interests? Do we keep the old date and old COI in the v1 table but use the newer date and current COI in the v2 table?

@cgreene
Copy link
Member Author

cgreene commented Mar 16, 2020

@agitter : Not ideal, but that was the only thing I could come up with, unless we added a display true/false flag and kept the old author metadata.

@agitter
Copy link
Collaborator

agitter commented Mar 16, 2020

Yeah, I don't have a great way to improve upon the current approach. When version 2.0 is close to finished, we could always manually update entries in the version 1.0 COI table.

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

Successfully merging this pull request may close these issues.

4 participants