Ability to copy / transfer entities to other spaces
D
David Jaggi
I would like to have the ability to move entities to another space. Let's say I develop some ideas in my personal space which become relevant to my work, I woulk like to move and/or copy them to a different space. There should be an option to move the linked entities aswell or at least the nodes which are directly linked.
Log In
M
Maximilian Canez Fernandes
This would be quite handy. The ability to move things around sure is a feature that would bring a lot of possibilities to the users, specially when the same can be shared/used in another space. I don't see any logical reason not to allow this. I mean, if the feature comes true it would save a lot of time and effort.
M
Mary North
Would love a first step to simply be able to MOVE/COPY an object to a different space. No ongoing connection between the items, no expectation that links work or that object types and fields are shared. Just super simple MOVE/COPY.
My work is divided into "active desktop" and "file cabinet" type items. I want to use capacities to keep home inventory items and warranties, medical history, record of home improvement, all sorts of things I may want to look up someday, and have indexed and stored digitally rather than in a file drawer.
But I don't want my day-to-day search to be cluttered with that content. I want to put some content away in the "file cabinet" because I need to keep it, but not be bothered by it every day.
First step: let me move/copy an object into another space
Second step: search default is "this space only", as an option, "search all spaces"
That's all I want. For now ;)
v
vision assemblies
I am 120% in support of this – as generally for greater transparency between 'spaces', which should not be 'walled' in a PKM.
… but as someone pragmatically dependent, I put up a interim request to at least make possible a (more) seamless 'copy&paste' within Capacities and btw spaces.
– you might also wanna support that, as kind of 'addon':
@team: let me know if this 'splicing' seems counterproductive. I am also happy to see it 'sorted' together, if that is the more convenien / helpful way…!
A
Aaron C
+1 to the idea of global objects that live in several workspaces. As an early believer with 1+ year using this great tool, I would say is my #1 ask on the wish list :)
Steffen Bleher
Steffen Bleher
v
vision assemblies
I´d join these ~200 voices / votes here
maybe also this general one is of interest to you:
A
Adam DAgostino
As a new user, I didn't know there were separate spaces until just now. I was first using 'tags' to try to filter my work from my personal projects, etc... I now understand that spaces are the best place for this. But now I have to manually copy everything over to the new space??? Seems like a horrible experience and a big waste of time.
Fix this for the sake of new users!
D
David Ventura
As a new user to capacities I started with a simple setup dividing work and personal (which really was anything not related to work.) However, now I'm considering a separate space for distinct areas of my life. For example I also have a side hustle as a Travel Agent and while I started to build content and transfer notes from other systems into my personal workspace. I'm just now realizing that I would want a workspace for my travel work, another for school, and another for my blog. My personal workspace would then be free to use for truly personal things like books, movies, friends, family, my health & wellness, or meal planning.
All this to say as workspace become larger, it warrants splitting into different workspaces. A transfer feature or event a bulk export/import option would be very valuable.
Steffen Bleher
Merged in a post:
Use the same Object Type across different Spaces
D
Derek P
Had sort of an "aha" moment today. Probably best to use an example to illustrate this concept. I currently have two spaces, a Work space and a Personal space. Within each space, I have a Persons object type, which for work I use to track people I take meetings with, and for personal I use to keep notes on friends and track if they recommend a movie or book.
For a while this worked well, until yesterday when a co-worker made a book recommendation to me. With this recommendation, my work and personal lives had just collided! And this got me thinking... What if an object type could exist across spaces?
As I started talking with folks on Discord, a few of us realized that the concept of Spaces is really helpful for dividing areas of our lives into different workspaces. The value in this is having distinct areas dedicated to very different parts of our lives, and we can click into one and write without being distracted by the other. But because these spaces don't talk to each other, instead of creating an ultimate "second brain" in Capacities, we are in fact creating third and fourth and fifth brains. Each space has essentially become an independent brain. Which unfortunately isn't exactly how our real brains work! So adding functionality to selectively connect Spaces together is what really could take Capacities to the next level as a PKM app.
As a first step in this connectivity, I think you could offer an option within an Object Type's settings menu to enable access to that object database across multiple spaces - this would be incredibly powerful. I'd suggest a checkbox system, whereby I could select which Spaces I'd want an object to show up in. By having this, I could have a single database for people across both Work and Personal spaces, and could link those people to both work and personal interactions I might be having.
I understand this may create complexities because of how Capacities is structured, but hopefully this is an idea that could evolve Capacities into the ultimate PKM, where right now I feel a bit constrained in how I need to "bucket" work and life between different spaces, when in fact there are cases where the two overlap.
Some have suggested that I just have a single Space for all my knowledge. I know this would fix my issue, but I find a lot of value in having separation between the two, so that I can really deep dive work and not be distracted by a personal project I'm working on, and vice versa, shut off work when I'm ready to and pivot into some personal passion projects.
I'm happy to be a sounding board if the development team has any further questions about how this type of structure might work best. I have additional thoughts about how collections might work in this format, meaning I basically think you'd need to have the ability to "nest" collections so that I could still separate my work collections from my personal collections.
Thanks for considering!
Load More
→