Quantcast

Duplicating items in lists intentionally.

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Duplicating items in lists intentionally.

Michael C Tiernan
I have a habit of creating a place at the highest level I can prove, such as "Massachusetts, USA" and then when/if I find out it's "Boston, Suffolk, Massachusetts, USA", I duplicate that first entry, and make a second one with more detail and when I find out it's "7 Main St....", I duplicate the "Boston" entry and fill in the greater detail of "7 Main", etc.

First question is, am I being dense about this and it conflicts with "good ways to do things" or is it a reasonable approach?

If it's reasonable, is there an easier way to duplicate an entry for something (such as Place/Locations) than retyping all the info again?

I'm not adverse to typing, I'm just adverse to goofy missteaks. ;)

This duplication request also applies to other items in the interface, such as Sources, Repositories, etc. not just Locations.

Thanks for everyone's time.

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Duplicating items in lists intentionally.

Benny Malengier
Interesting suggestion.

What would be needed is to allow drop of the clipboard of a place on a place editor, and use the drop to set all data.
Or a duplicate button, but that seems like interface clutter to me.

Other ideas to allow this?

If you don't mind cut and paste, you can duplicate by exporting this one place to .gramps (or editing an xml in .gramps to only contain this one place) and then import will create a duplicate. editing the xml will however take you just as long as reentering the data I'm afraid.

Benny


2012/4/17 Michael C Tiernan <[hidden email]>
I have a habit of creating a place at the highest level I can prove, such as "Massachusetts, USA" and then when/if I find out it's "Boston, Suffolk, Massachusetts, USA", I duplicate that first entry, and make a second one with more detail and when I find out it's "7 Main St....", I duplicate the "Boston" entry and fill in the greater detail of "7 Main", etc.

First question is, am I being dense about this and it conflicts with "good ways to do things" or is it a reasonable approach?

If it's reasonable, is there an easier way to duplicate an entry for something (such as Place/Locations) than retyping all the info again?

I'm not adverse to typing, I'm just adverse to goofy missteaks. ;)

This duplication request also applies to other items in the interface, such as Sources, Repositories, etc. not just Locations.

Thanks for everyone's time.

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users


------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Duplicating items in lists intentionally.

Michael C Tiernan
----- Original Message -----
> Or a duplicate button, but that seems like interface clutter to me.

I don't disagree but I want to point out that the inverse already exists. I can take two entries (just about any two from almost any list) and select "Merge". It just seems to me that "logically" {*cough*} there ought to be a "Split" option right next to the merge option.

I've already proven that in the location list, I can have two identical entries so forming a duplication of the existing entry isn't ruled out, the only thing (that I can tell from here) that might be an issue is the "References" pointers, do you duplicate them too? I am of the opinion that at the point of confirmation of the task you can have a check-box for "duplicate references" or clear them all in the new entry.

Thanks for everyone's time!

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Duplicating items in lists intentionally.

Ron Johnson
On 04/18/2012 07:12 AM, Michael C Tiernan wrote:
> ----- Original Message -----
>> Or a duplicate button, but that seems like interface clutter to me.
>
> I don't disagree but I want to point out that the inverse already exists. I can take two entries (just about any two from almost any list) and select "Merge". It just seems to me that "logically" {*cough*} there ought to be a "Split" option right next to the merge option.
>
> I've already proven that in the location list, I can have two identical entries so forming a duplication of the existing entry isn't ruled out, the only thing (that I can tell from here) that might be an issue is the "References" pointers, do you duplicate them too? I am of the opinion that at the point of confirmation of the task you can have a check-box for "duplicate references" or clear them all in the new entry.
>
> Thanks for everyone's time!
>

+1 on the desire for a Duplicate button.

--
"There is usually only a limited amount of damage that can be
done by dull or stupid people. For creating a truly monumental
disaster, you need people with high IQs."
Thomas Sowell

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Duplicating items in lists intentionally.

DS Blank
On Wed, Apr 18, 2012 at 12:03 PM, Ron Johnson <[hidden email]> wrote:

> On 04/18/2012 07:12 AM, Michael C Tiernan wrote:
>> ----- Original Message -----
>>> Or a duplicate button, but that seems like interface clutter to me.
>>
>> I don't disagree but I want to point out that the inverse already exists. I can take two entries (just about any two from almost any list) and select "Merge". It just seems to me that "logically" {*cough*} there ought to be a "Split" option right next to the merge option.
>>
>> I've already proven that in the location list, I can have two identical entries so forming a duplication of the existing entry isn't ruled out, the only thing (that I can tell from here) that might be an issue is the "References" pointers, do you duplicate them too? I am of the opinion that at the point of confirmation of the task you can have a check-box for "duplicate references" or clear them all in the new entry.
>>
>> Thanks for everyone's time!
>>
>
> +1 on the desire for a Duplicate button.

I like the idea of a split/duplicate function as well. Now, someone
needs to make a feature request:

http://gramps-project.org/wiki/index.php?title=Using_the_bug_tracker

Thanks!

-Doug

> --
> "There is usually only a limited amount of damage that can be
> done by dull or stupid people. For creating a truly monumental
> disaster, you need people with high IQs."
> Thomas Sowell
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Gramps-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-users

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Duplicating items in lists intentionally.

Michael C Tiernan
----- Original Message -----
> I like the idea of a split/duplicate function as well. Now, someone
> needs to make a feature request:

Done:

http://www.gramps-project.org/bugs/view.php?id=5692

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Loading...