![]() comments: would be better to have there and record than having in a slack thread, scattered in different channels.the back-link reference: having the entities in the content highlighted is great, allow to navigate easily to those entities, but it is nice to have (the user could do a search in Fibery), the real value is the back-link, having a list of relevant Articles when looking at any Entity.In systems like Notion, there are more chances that someone creates a duplicate entry since there is no concept of types by linking the entities we ensure that there is one unique entity.I also have an Article entity type, and I would like to easily record all articles that are relevant to my company and linked them to the entities (Organization, Services, etc). If an Organization is a client, it is linked to an Account entity in the CRM app. The Services themselves have fields to described if they are competitors to one of our services, or if they are a potential tech or data provider, etc. ![]() client + being a data provider to us) I have created an entity type Organization, with several fields to describe the relationship, and an entity type Service to describe the services that this organization provides. Since one organization can have several hats (eg. I want to keep knowledge of all the organizations in our space (clients, competitors, providers, partners, companies in our ecosystems). I cannot do that with Notion for example, since everything is a page/document and not a structured entity. It is important to keep track of thoses.Īnd once the web page is in Fibery, we have all the power of Fibery to link to unique Entities, comments, highlights, etc. The point of Fibery is to organize our knowledge, part of it comes from “raw sources” that are web pages and documents. Especially, in this case, it is not complicated to have a simple chrome extension that saves the page to an Entity (need access to Fibery API and authentication to the user account). Maybe my need for articles precisely is a bit too specific, but at least a chrome extension that saves content, url, pdf is a generic one.Īnd I agree with that the point of Fibery is to avoid too many integration tools. Having the content and not just a link is also important to avoid losing information if the web page is deleted. Back linked would also allow seeing all articles referring to a specific Entity. Contrary to Notion or other similar tools, the value is that the content can be edited to enrich with Entity links, comments, etc. The idea is to have a collection of relevant articles that the team curate, regarding our market, competition, etc. potentially also keeping a pdf version of the article attached, to be able to see original formatting potentially highlighting entity match in the content to create links to EntityĮ. for articles the chrome extension would fill the content with the page content, extract the author, publication, and article name (using semantic when the page follows standards like or inferring), also adding tags based on metadataĭ. Entity type with name, content (rich text), URL, author, publicationĬ. chrome extension to save (and decide which type to create if implemented with 2.)ī. I have a need specifically for article type of HTML pages. let the users create Entities type that have an “web page” extension that we ensure the default field are created and set when a page is saved.Since Fibery aimed is to organize information, having a way to “save” web pages into either
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |