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

Create personal profile documents for each member #79

Open
7 of 10 tasks
cdchapman opened this issue Aug 20, 2018 · 1 comment
Open
7 of 10 tasks

Create personal profile documents for each member #79

cdchapman opened this issue Aug 20, 2018 · 1 comment

Comments

@cdchapman
Copy link
Member

cdchapman commented Aug 20, 2018

See my thoughts on the Linked Research document of FORCE11 SCWG4 for some context.

  • Merge author pages into personal profiles
  • Create turtle representation of the pages using the rdf_distiller filter.
  • Remove author pages and create 301 redirections from author pages to personal profile pages
  • Link from the roster to the personal profile document
  • Create WebIDs and add certificates for WebID+TLS authentication

Question: how do we handle it when someone has an personal profile document somewhere else? We could (1) fetch the document and use it as a data source from which to pull relevant personal info (2) create another profile for them and link or redirect to their original profile.

Regarding this question, I think we:

  • Create a etc/people.yaml file with names of people that we have referenced in the content and their WebID, if any.
  • Support explicit metadata fallback for people without WebIDs. Create a command to fetch and cache data and images from these people's personal profile documents.
  • Create a data source to build internal Nanoc items from the etc/people.yaml file and a helper to access these people items from a layout.
  • Use these data to build a people index at /people/index.erb that lists company members in addition to other people that may have authored or have been referenced in the content of the site. If a person has no WebID, only their name will show up (along with links to the content in which they were referenced), but if they have a WebID, we will augment their listing with a photo, title, etc., and link to their personal profile document.

This way we only create personal profile documents for company members (as needed). The index shouldn't care whether the personal profile document is on this site or somewhere else. It should treat them all identically.

  • (optional) Create a filter that finds the name of any person in the content and marks it up as a foaf:Person with their WebID.
@cdchapman cdchapman changed the title Create personal profile documents for each person Create personal profile documents for each member Oct 7, 2019
@cdchapman
Copy link
Member Author

cdchapman commented Oct 23, 2019

I think we should generate personal profile documents for all members, even if they have another WebID and personal profile document somewhere else on the Web. (We can connect them with owl:sameAs).

This way we can keep a company-specific profile document for every member.

cdchapman added a commit that referenced this issue Oct 23, 2019
Fixes #85 and parts of #79.

Separates out the concept of a company member and any other person.
Assigns a local identifier if a web_id is not provided, so every person
  has a unique and stable identifier.
Updates relevant filters for greater clarity and to these identifiers.
Populates web_id during preprocessing as an item attribute rather than
  providing a function to dynamically assemble during buildtime.
Provides a new data source for people.
@cdchapman cdchapman pinned this issue Dec 28, 2021
@cdchapman cdchapman added this to the 3.0 milestone Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant