-
Notifications
You must be signed in to change notification settings - Fork 1
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
Labels
Milestone
Comments
cdchapman
changed the title
Create personal profile documents for each person
Create personal profile documents for each member
Oct 7, 2019
cdchapman
added a commit
that referenced
this issue
Oct 21, 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 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
added a commit
that referenced
this issue
Oct 24, 2019
cdchapman
added a commit
that referenced
this issue
Oct 24, 2019
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See my thoughts on the Linked Research document of FORCE11 SCWG4 for some context.
rdf_distiller
filter.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:
etc/people.yaml
file with names of people that we have referenced in the content and their WebID, if any.etc/people.yaml
file and a helper to access these people items from a layout./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.
foaf:Person
with their WebID.The text was updated successfully, but these errors were encountered: